S5 - Gpon 10142013 PDF
S5 - Gpon 10142013 PDF
Distribution: 12/2012
S511
S506
User's Guide
| Copyright |
Copyright © 2004 by Corecess Inc. All rights reserved.
| Trademark Credit |
Corecess S5 System is registered trademark of Corecess Inc.
Corecess Inc.
-Sales and R&D: 2-3/F #674-4 Bokjung-Dong, Sujung-Gu,
Sungnam City, Kyunggi-Do, 461-831, Korea
Tel: +82-31-739-6815(Sales)
www.corecess.com
Manual Contents
Manual Contents
This instruction consists of following materials about Corecess S5 System which is multi-
functional broadband platform from Corecess Inc.
Introduction to functions and features
Name and function of each part
How to install on a rack and connect cable to each port
How to configure the Corecess S5 System
The user should read the chapters 1~3 with being included the functions of the product, name and function
of each part, and the precautions before installation. Understanding chapters 1~3 will help a great deal for
safety in installing and using the product.
Note: You can flexibly configure S5 system with using chassises,SCMs and LIMs.
If you have any problems or questions during installation or while using the product, contact
your equipment provider or visit our website at www.corecess.com and leave a message in Q&A.
Audience
This manual is designed for the users with basic knowledge in Ethernet and FTTx. Thus, this manual
assumes that the reader is knowledgeable of basic concepts and terminology about Ethernet and FTTx and
does not provide separate explanations for these topics. If you feel that the contents of this manual are
difficult and require more detailed explanations, refer to other network related books.
Revision History
Edition Date Description
0003 2012. 12 ss5g-base-osapp-REL1.0.1.RC42.img
0002 2010.7 ss5g-base-osapp-REL1.0.1.RC35.img
0001 2010.4 First Draft
III
Notations
Notations
This manual uses the notations explained below for assisting readers in understanding the
contents of this manual.
{ A | B | C } means that one entry among A, B, and C must be selected and entered.
[A | B | C] means that one entry among A, B, and C may or may not be selected and
entered.
Conventions
This manual uses the following conventions:
Note: Introduces useful item for the use of product, reference, and its related materials.
Warning: Explains situtations in which product can be damaged or danger can be imposed
to users physically, and informs you how to respond to those situations.
Caution:
After set commands in the global configuration mode, you must execute ‘write’ commands for
saving.
To show running information, you execute “show” commands in the priviledged mode.
Caution:
The value of slot/port may differ according to the each equipment.
The showing of system information may differ according to the software version of the
equipment.
V
Organization
Organization
The chapters of this manual are organized as follows:
Chapter 1 Overview
This chapter introduces the Corecess S5 System functions and features.
This chapter introduces the structures of the front and rear side of the Corecess S5
System and describes the function and appearance of the modules provided for the
Corecess S5 System. This chapter also briefs the devices connected to the Corecess S5
System.
Chapter 3 Installation
This chapter describes how mount the Corecess S5 System on a rack, install the
SCM/LIM module and connect the cables to the ports.
VII
Organization
Appendix C Maintaining
This chapter describes how to maintain the Corecess S5 System.
Table of Contents
IX
Table of Contents
XI
Table of Contents
XIII
Table of Contents
XV
Table of Contents
XVII
Table of Contents
List of Tables
XIX
List of Tables
XXI
List of Tables
XXIII
List of Tables
Chapter 1 Overview
Introduction
S5 Series
The Corecess S5 System is multi-functional platform used as AON switch, E-PON OLT, G-PON
OLT and WDM-PON OLT on Ethernet-based fiber optic network. The Corecess S5 System
provides TPS (Triple Play Service) solution that integrates broadband Internet, Broadcasting
and telephone service.
E-PON OLT : Ethernet Passive Optical Network OLT (Optical Line Terminal)
The S5 platform is high performance switch router that acts as PON OLT and Ethernet
Aggregation Switch. It provides various optical links while generating and controlling the
services. It offers the optical links of GEPON, G-PON, Gigabit Ethernet and also acts as OLT for
WDM PON if it combines with WDM multiplexer. The S5 platform makes access network
simple by integrating multiple functions into a single scalable platform. With its high
functionalities and scalability, it enables both of residential and commercial services with a
single platform.
The S5 consists of various Switching & Control Module(SCM) and Line Interface Module(LIM).
The capacity of back plane, SCM and LIM are scalable in terms of throughput and density. The
10 Gigabit Ethernet is ready for the service of today and future. SCM and LIM are compatible
between chassis to implement a system with mix and match. With this modular designs, it
provides the great flexibility for operators to have wide ranges of options depending on their
services and density while keeping simplicity with same function and performance.
The Corecess S5 System supports the high performance QoS. Thus, the user can control several
kinds of traffic (voice, video and other important data) efficiently. The Corecess S5 System
provides reliable service that gives important packets high priority and processes the packet
faster than others. The Corecess S5 System is easy to use and can be easily installed as well. And
LEDs on the front panel of the Corecess S5 System make it easy to manage the product and
networks through notifying the operation status, port conditions and fault occurrence.
Overview 1-3
Hardware Features
Hardware Features
SCM(Switching & Control Module)
Table 1-2 SCM
Chassis
S511 - 2 SCM slots, 8 LIM slots, 7 RU, DC/AC
S506 - 1 SCM slot, 4 LIM slots, 4 RU, DC/AC
Slot Configuration
Slot composition according to Corecess S5 chassis is as follows;
Future proofed optical links : G-PON, GEPON, Gigabit Ethernet, WDM PON
Capacity of backplane and SCM, throughput speed of interface and port density are scalable
SCM and LIM are common and compatible for 2 different types of chassis
Hardware based high speed(Max 2.5G per Port) Dynamic Bandwidth Allocation
GPON OLT based on the ITU-T G.984 standard
Full ITU-T G.984 GPON OLT functionality.
Wire speed processing
On-chip embedded reassembly buffer per GPON channel
Supports up to 128 ONTs per GPON channel
Supports upto 4095 GEM port-id per GPON channel
Supports up to 512 Alloc-IDs per GPON channel
128-bit Advanced Encryption Standard (AES) encryption engine for PON security and privacy with
up to 128 unique keys.
Flexible optical transceiver interface for multiple vendor support.
ITU-T G.984-compliant
• Virtual Scope – GPON network digital diagnostics function
• Full management of the ONT through an ITU-T G.984 Operation Management Control
Interface (OMCI) protocol.
Overview 1-5
Hardware Features
Graceful restart
Software Features
Layer 2 Switching
Supports Port based VLAN and IEEE 802.1q tagged VLAN (maximum: 4,096)
The Corecess S5 System supports Layer 3 switching. Because Layer 2 switches don’t support the
Layer 3 communication between VLANs, a separate router is needed to link the VLANs. But the
Corecess S5 System supporting Layer 3 switching can process all incoming packets without a
separate router.
OSPF
IS-IS
BGPv4
VRRP
multiple priority queue support, congestion control, traffic shaping & policing and modification
Overview 1-7
Software Features
DVMRP
MVR
IPTV Service
Security
Supports CIFS filtering using MAC address, IP address and TCP/UDP port number
Protection from IP/ARP spoofing, packet storming & TCP sync flooding
Network Management
The Corecess S5 System supports SNMP (Simple Network Management Protocol), RMON
(Remote MONitoring) and port mirroring for network management. You can monitor and
control the Corecess S5 System network via the console port, Telnet session, or the Corecess
NMS, ViewlinX.
Port Mirroring
The Corecess S5 System allows you to use the port mirroring function without affecting the switching
performance.
RMON
The Corecess S5 System provides four RMON groups (history, statistics, alarms, and events) in each
port as traffic management, monitoring and analysis tools.
Overview 1-9
Software Features
The Corecess S5 System provides easy-to-upgrade using FTP and TFTP in a remote place.
Hardware Description
This chapter introduces the structures of the front and rear side of the Corecess S5 System and describes
the function and appearance of the modules provided for the Corecess S5 System. This chapter also briefs
the devices connected to the Corecess S5 System.
Overview 1-11
System Chassis
System Chassis
This section describes the external features of the Corecess S5 System chassises.
Corecess S5 consists of various chassises and SCM(Switching Control Module), LIM(Line
interface Module). Those help operator with flexible and economical configuration environment
enough to achieve the aimed network.
S511 Chassis
Front View
11 Slots: 2 SCM + 8 LIM + 1 Power slot
7 RU, ETSI compliant form factor Switching and Control Module (SCM)
Full front access 1:1 Protection
MAX 160Gbps backplane capacity SCM-B208G
MAX 20Gbps slot capacity 208G Switching Fabric
4x10GbE + 8xGbE SFP for uplink
There are ten slots, rack blanket, fan tray and fan filter in front of Corecess S511 system. The
SCM and LIM module are equipped in the slots, and a back-plane board inside the chassis
makes SCM and LIM module communicate each other. Three power modules supply the
Corecess S511 system with the ensured power. The default state of two of them is running and
that of the other is under earmark for stand-by. In the emergent event of a failure of source
power to one supply, or the failure of one power supply, the redundant power option
guarantees stable and uninterrupted operation. LIM module can be installed up to 8 from
bottom.
Back Plane
Slot
SCM Slot (10)
SCM Slot (9)
LIM Slot (8)
LIM Slot (7)
LIM Slot (6)
LIM Slot (5)
LIM Slot (4)
LIM Slot (3)
LIM Slot (2)
LIM Slot (1)
S511 Features
Power is supplied in the form of module with DC -48V. Three power modules supply the
Corecess S511 system with the ensured power. The default state of two of them is running and
that of the other is under earmark for stand-by. The function of hot swapping provided by
Corecess S511 system allows operator to add, replace or remove any modules without
interrupting or shutting down the system power or interfaces. The 9 and 10 number of SCM
modules are under control of redundancy.
Overview 1-13
System Chassis
S506 Chassis
There are five slots, rack bracket, fan tray and fan filter in front of Corecess S5 System. The SCM
and LIM module are equipped in the slots, and a back-plane board inside the chassis makes
SCM and LIM module communicate each other. The Corecess S506 provides maximum two AC
power modules.
S506
View
Back Plane
Slot
The Corecess S506 has five slots in which one SCM module and four LIM modules can be
installed. The SCM module takes charge of switching and system control, and the LIM modules
provide G-PON interface. When you execute CLI commands for system configuration or
monitoring, use the slot number. Each slot’s type and number is as follows:
S506 Feature
The AC power modules supplies AC power (100V~220V) to the Corecess S5 System. The
Corecess S506 supports redundant AC-input power supplies. In the event of a failure of source
power to one supply, or the failure of one power supply, the redundant power option ensures
uninterrupted operation.
Overview 1-15
Chassis Items
Chassis Items
Table 1-6 Slot Description
Slot Description
SCM Slot Installation of SCM modules that control overall performance of system and provide
switching functions
The Corecess S5 System’s slots support hot-swap function, and you can install a module into the
slot without turning the system off.
Note : For more information of modules, ports and LEDs, refer to System Modules in this
chapter.
<Corecess S506>
AC Power AC Power
Module Module
Rack Bracket
The rack bracket is used when equipping the Corecess S5 System to install it on a 19-inch rack.
Chapter 4 Installation describes how to mount the Corecess S5 System with a rack bracket on a
19-inch rack.
Fan Tray
The system fan comes with cooling fan that maintain proper temperatures inside the chassis.
The LED on the fan tray denotes power supply and operating status. During the fan module
operates normally, the LED is lit on green. When a user stops operating the cooling fan, the LED
is lit on orange. When the cooling fan has a problem, the LED is lit on red.
Fan Filter
The fan filter filters dust which comes into the system through the ventilation holes. The fan
filter should be checked depend on cleanliness of the location, and replaced or cleaned if
necessary.
Overview 1-17
SCM Module
Ground Terminal
The ground terminal is a terminal for the system ground. Connect the ground terminal to the
external ground using ground for preventing an electric shock or the system damage .
A ground terminal is on the rear of chassises.
Ventilation Holes
The ventilation holes are where heat, which is generated while the Corecess S5 System is
operating, comes out and external cold air is taken in. If the ventilation holes are blocked when
using the Corecess S5 System, the product may overheat because the internal hot air and
external cold air cannot circulate properly.
SCM Module
The Corecess S5 system provides the following SCM module:
SCM-B208G
SCM-B208G is switching control module that provide system control function and Layer 3
switching. SCM-B208G module provides 8 Gigabit Ethernet uplink ports (SFP type), four 10G
Ethernet uplink ports(XFP type), console port and ethernet port.
SCM-B68G
SCM-B68G is switching control module that provide system control function and Layer 3
switching . SCM-B68G module provides 8 Gigabit Ethernet uplink ports (SFP type), two 10G
Ethernet uplink ports(XFP type), console port, and ethernet port.
Overview 1-19
SCM Module
Switching fabric capacity 68G full duplex (68G aggregate) 208G full duplex (208G aggregate)
Memory
Table 1-10 Memory
Note: Master LED is only operated when two SCM modules are installed in the system for
redundancy.
Overview 1-21
SCM Module
Port Type
The console port is used to connect a console terminal for monitoring and configuring the
Corecess S5 System. To connect the console port to a console terminal, use the included console
cable. A PC or a workstation installed with a terminal emulation program or VT-100 terminal
can be used as a console terminal.
The Ethernet Management port is used for connecting the Corecess S5 System to the network to
manage the system by the NMS (Network Management System) or Telnet. The Ethernet
Management port is a 10/100Base-TX port. In connection with 10/100Base-TX port, the speed
(10Mbps or 100Mbps) and the transmission mode (full-duplex or half-duplex) are automatically
configured in accordance with the speed and transmission mode of the connected device. The
cables for connecting to the Ethernet Management port are twisted-pair category 3, 4 and 5 with
RJ-45 connectors at both ends.
The following table describes the information indicated by the Ethernet Management port LEDs:
Table 1-12 LED Functions of Ethernet Management Port on the SCM Module
The Gigabit Ethernet port is an uplink port connected the Corecess S5 System to core network.
XFP 10GBaseR uplink port requires additional 10GbE XFP transceiver.
The following table lists the specifications of the Gigabit Ethernet port on the SCM module:
GbE Port(SFP)
The following table describes the information indicated by the port LEDs:
Overview 1-23
LIM Module
LIM Module
The Corecess S5 system provides the following LIM module:
The 2.5G-PON SFP Port is connected to the maximum number of 64 ONT(Optical Network
Terminal) through a splitter.
The following table lists the specifications of the 2.5G-PON SFP Port.
Feature Specification
Transfer Mode Full-duplex mode
Transfer Speed Downstream :2.5 G bps, Upstream : 1.25Gbps
Connector Type SC Receptacle SFP
Optic Specification Class B+, Class C, Class C+
Compliance G.984.1, G.984.2, G.984.3, G.984.4, G.984.5
Branch Number per Port 128
Alloc-IDs per port 512
Port-IDs per port 4095
MAC addresses per port 4095
Rx : 1310nm Single mode fiber optic cable
Transfer Media
Tx : 1490nm Single mode fiber optic cable
Caution: Do not stare into the aperture of a fiber-optic port. Invisible radiation might be
emitted from the aperture of the port when no fiber cable is connected. Thus, if you don’t
use the fiber optic port for a long time during the system operation, Close the port with a cap
or Connect the port with a fiber optic cable.
Run LED
Port LED
Overview 1-25
LIM Module
Redundancy
Precautions
Warning: Before you install the Corecess S5 system, read this section. This section
contains important safety information you should know before working with the system.
General Precautions
While or after installing the equipment, keep the equipment clean and free from dust all the
time.
After removing the cover of the equipment, keep the cover in safe place.
Any tool or cable should not be left on the way of passage for better safety.
When installing the equipment, the installer should not wear baggy clothing so that tie, scarf,
and sleeves should not be caught in the equipment. Keep tie and scarf from getting slack,
and roll up the sleeves.
Avoid any harmful action that damages the people or the equipment.
In case that opening the case for repairing or test is required, contact the sales agency where
you purchased this equipment, or directly contact Corecess Inc. for professional help.
Power Considerations
Be careful when connecting the system to the supply circuit so that wiring is not overloaded.
When plugging in a power socket or handling any power source, avoid ring, necklace, metal
watch for better safety. If these materials touch the power socket or ground of the product,
the parts can be burnt out.
Always verify whether there is any possible danger in the workshop. Wet floor, ungrounded
extension, rubbed-off power code, or unsafe (or ungrounded) floor might be dangerous.
DC Power
Connect DC-input power supplies only to a DC power source that complies with the safety
extra-low voltage (SELV) requirements in the UL 1950, CSA 950, EN 60950, and IEC 60950
standards.
Ensure that power is removed from the DC circuit before installing or removing power
supplies. Tape the switch handle of the DC circuit breaker in the off position.
Use approved wiring terminations, such as closed-loop or spade-type with upturned lugs,
when stranded wiring is required. These terminations should be the appropriate size for the
wires and should clamp both the insulation and the conductor.
Ensure that no exposed portion of the DC-input power source wire extends from the
terminal block plug. An exposed wire can conduct a harmful level of electricity.
AC Power
The system is designed for connection to TN power systems. A TN power system is a power
distribution system with one point connected directly to earth (ground). The exposed
conductive parts of the installation are connected to that point by protective earth conductors.
Ensure that the plug-socket combination is accessible at all times, because it serves as the
main disconnecting device.
Spare Power
If you purchase the product whose a spare power supply is installed, two power supplies are
connected to each input power. Then, if one of the power supplies is not working, the system
can be operating continuously.
Preventing ESD
Electrostatic discharge (ESD) damage occurs when electronic cards or components are
mishandled and can result in complete or intermittent failures. Note the following guidelines
before you install or service the system:
Always wear an ESD-preventive wrist or ankle strap when handling electronic components.
Connect one end of the strap to an ESD jack or an unpainted metal component on the system
(such as a captive installation screw).
Handle cards by the faceplates and edges only; avoid touching the printed circuit board and
connector pins.
Handle cards by the faceplates and edges only; avoid touching the printed circuit board and
connector pins.
Avoid contact between the cards and clothing. The wrist strap only protects the card from
ESD voltages on the body; ESD voltages on clothing can still cause damage.
For safety, periodically check the resistance value of the antistatic strap. The measurement
should be between 1 and 10 Mohms.
Remove all jewelry (including rings and chains) or other items that could get caught in the
system or heat up and cause serious burns.
Do not touch the backplane or midplane with your hand or metal tools.
Do not perform any action that creates a potential hazard to people or makes the equipment
unsafe.
Disconnecting Power
Locate the emergency power-off switch for the room before working with the system.
Turn off the power and disconnect the power from the circuit when working with
components that are not hot-swappable or when working near the system backplane or
midplane. If the system does not have an on/off switch, unplug the power cord.
To completely de-energize the system, disconnect the power connection to all power supplies.
For DC power supplies, locate the circuit breaker on the panel board that services the DC
circuit, switch the circuit breaker to the off position, and tape the switch handle of the circuit
breaker in the off position.
Do not touch the power supply when the power cord is connected. Line voltages are present
within the power supply even when the power switch is off and the power cord is connected.
Connecting Cables
Use caution when installing or modifying telephone lines to prevent electric shock.
Do not work on the system or connect or disconnect cables during periods of lightning activity.
Do not touch uninsulated telephone wires or terminals unless the telephone line has been
disconnected at the network interface.
Hazardous network voltages are present in WAN ports regardless of whether power to the
system is off or on. When you detach cables, detach the end away from the system first.
Do not use a telephone to report a gas leak in the vicinity of the leak.
Do not install telephone jacks in wet locations unless the jack is specifically designed for wet
locations.
To avoid exposure to radiation, do not stare into the aperture of a fiber-optic port. Invisible
radiation might be emitted from the aperture of the port when no fiber cable is connected.
Always keep unused fiber-optic ports capped with a clean dust cap.
Preventing EMI
When you run wires for any significant distance in an electromagnetic field, electromagnetic
interference (EMI) can occur between the field and the signals on the wires.
Strong EMI, especially when it is caused by lightning or radio transmitters, can destroy the
signal drivers and receivers in the system, and can even create an electrical hazard by
conducting power surges through lines and into the system.
If Strong EMI occurs in the installation place, consult RFI experts to get rid of it.
Ensure that all cards, faceplates, and covers are in place. Blank faceplates and cover panels are
used to:
Help contain electromagnetic interference (EMI) that might disrupt other equipment
Install the system in an open rack whenever possible. If installation in an enclosed rack is
unavoidable, ensure that the rack has adequate ventilation.
Maintain ambient airflow to ensure normal operation. If the airflow is blocked or restricted,
or if the intake air is too warm, an over temperature condition can occur.
Avoid placing the system in an overly congested rack or directly next to another equipment
rack. Heat exhaust from other equipment can enter the inlet air vents and cause an over
temperature condition.
Equipment near the bottom of a rack might generate excessive heat that is drawn upward
and into the intake ports of the equipment above. The warm air can cause an over
temperature condition in the equipment above.
Ensure that cables from other equipment do not obstruct the airflow through the chassis or
impair access to the power supplies or cards.
Load the rack from the bottom to the top, with the heaviest system at the bottom.
If there is equipment already installed in the rack, select the location for the system carefully
considering the size of the system:
Ensure that your footing is solid and the weight of the system is evenly distributed between
your feet.
Lift the system slowly, keeping your back straight. Lift with your legs, not with your back.
Bend at the knees, not at the waist.
Do not attempt to lift the system with the handles on the power supplies or on any of the
cards. These handles are not designed to support the weight of the system.
To lift and move the system, following number of people or a crane should be needed
depends on weight of the system:
Below 18Kg 1
18~32Kg 2
32~55Kg 3
Installation Place
Environmental Requirements
For the safe installation and use of the Corecess S5, the place for installation should satisfy the
following requirements:
While or after installing the product, keep the product clean all the time.
The system should be installed in a cool place where has no direct ray of sunlight. Any tool
or equipment should not be place on the way of passage.
The following ambience condition for temperature and humidity should always be kept.
Item Temperature
Power Supply
The Corecess S5 should be installed in the place where power supply satisfying the following
condition is provided.
Verify the power (source) be clean. If there is too much noise or spark, it is better to have the power
control equipment.
Locate an electric outlet near the system for easy installation of power cable.
Be careful with connecting power supply equipment and avoiding overload wiring.
Unpacking
As the following instructions, unpack the shipping carton and inspecting contents of the
shipping carton.
1. Open the shipping carton of the Corecess S5. There is this manual, desiccant, a power
cable(s), and a console cable on the cushion inserted- Corecess S5 system.
2. Without taking off the cushions, pick out the equipment with two hands, and put it in a safe
place.
3. And then, verify whether there is a plastic bag that contains rack brackets and
screws under the shipping carton.
Corecess S5 System
binder-head screws
Recommendation: After unpacking, do not throw away the box including cushions and
keep them in a safe place in case the product is relocated, it is better to move the product
after packing with the box including cushions.
Note: If there are some missing contents or damaged components, contact the sales
agency where you purchased this product to replace them with new ones.
Chapter 3 Installation
This chapter describes how mount the Corecess S5 System on a rack, install the SCM/LIM module and
connect the cables to the ports.
Installation Procedure
Installation Procedure
The following summarizes the installation procedure for the Corecess S5. The next section will
describe in detail the step-by-step procedures for each step.
Rack-mount
The design allows the Corecess S5 System to be mounted on a 19-inch rack. The
1
screws needed for rack mounting are enclosed with the product.
Installing modules
2 Install SCM/LIM modules in the slots of the Corecess S5 system.
.
Connect network devices
Connect Gigabit Ethernet ports or PON ports on the SCM/LIM modules with
3
other network devices using appropriate network cables.
Rack-Mounting
The design allows the Corecess S5 System to be mounted on any kind of standard 19-inch racks.
This section describes how to install the Corecess S5 System on a 19-inch rack.
Caution: Before installing the system in a rack, read the Rack-Mounting the System section
in the Chapter 3 Before Installation to familiarize yourself with the proper site and
environmental conditions.
Make sure that the 19-inch rack is placed on a convenient location for the Corecess S5 System
installation. At least, the space of 550 x 750 (width x length)mm is needed to install the 19-inch rack.
Check to see if there is a vertical space of around rack units in the rack because of the Corecess S5
System and air flow space (1U).
Coreces S511(7U)
Installation 3-3
Rack-Mounting
A screwdriver
Four (4) binder-head screws (M5, 8mm) (provided along with the product)
Note: For more information about ESD, refer to the Chapter 3/ Before Installation.
Once all the tools and equipment are prepared, mount the Corecess S5 on a 19-inch rack
according to the following procedure:
1. Place the Corecess S5 on a spacious floor or a sturdy table near the rack. And check the
tools and materials.
2. Lift up the Corecess S5 as high as the available space in the 19-inch rack.
3. Place the rack brackets installed on the Corecess S5 to the holes of the 19-inch rack. And fix
the brackets using four (4) binder-head screws.
Caution: The following explanations should be noticed when installing the Corecess S5 into
the 19-inch rack:
Locate the heavy things at the bottom of the rack. If there is another equipment already
installed in the rack, select the location for the Corecess S5 carefully considering the size
of the Corecess S5.
If the rack is empty, you should install the Corecess S5 System at the bottom of the
rack.
Installation 3-5
Installing Modules
Installing Modules
The Corecess S5 System has five slots, and the following types of module can be installed.
This section describes how to install modules in the Corecess S5 System slots.
Note: Place the removed module where there is no static electricity or keep it in an anti -
static envelop.
3. When installing a module in an empty slot, loosen the screws on the blank bracket that
blocks the empty slot. And remove the blank bracket.
Note: When LIM module’s installation, it is convenient that installation proceed from the
number 1 slot in order.
4. Prepare a module that is to be installed. Check to see if there is any defect by examining the
exterior of the module.
5. Place module to the guide rail that is located in the both sides of the slot. Then, insert the
module carefully until it gets installed in the connector of the back plane. And push the
ejectors located in the both sides of the module.
6. Fasten the module firmly by tightening the two screws using a screwdriver.
7. If the module is installed successfully, the Run LED on the module is turned on with green,
and then it is flashing. Connect cables to ports of the module, and configure the ports using
CLI commands if necessary.
Note: Since the Corecess S5 System provides the hot-swap functions, the system power
doesn’t have to be turned off.
Installation 3-7
Installing Modules
1. Attach an ESD-preventive wrist strap to your wrist and to a bare metal surface on
the chassis.
2. Take the SFP modules out of the packing and check carefully to see if there is any
defect.
Dust plug
Actuator Button
Note: External form of SFP module can be different according to SFP module manufacturer.
3. Align a SFP module in front of the SFP module slot facing the letter-printed side upward.
4. Insert the SFP module into the slot until you feel the connector on the module snap into
place in the rear of the slot.
Caution: Do not remove the dust plugs from the fiber-optic SFP module port or the rubber
caps from the fiber-optic cable until you are ready to connect the cable. The plugs and caps
protect the SFP module portsand cables from contamination and ambient light.
Installation 3-9
Installing Modules
1. Attach an ESD-preventive wrist strap to your wrist and to a bare metal surface on
the chassis.
3. Insert a dust plug into the optical ports of the SFP module to keep the optical interfaces
clean.
4. Press the actuator button to release the SFP module from the slot. Grasp the SFP module
between your thumb and index finger and carefully remove it from the module slot.
Actuator Button
5. Place the removed SFP module in an antistatic bag or other protective environment.
For the information of cables connected to each port, refer to Appendix B Connector and Cable
Specifications.
Caution: If the distance of two devices connected with a cable is farther than the distance
described in this manual, data can be lost during the transmission.
Installation 3-11
Connecting Network Devices
The 1000Base-SX/LX SFP module can be installed in the SFP slot of the SCM module and the
Corecess S5 System can be connected to the core network using the 1000Base-SX/LX SFP
module. Depends on the type of SFP modules, connect cables as follows;
SCM-B208G
Installation 3-13
Connecting Network Devices
Prepare the single mode fiber optic cable, then connect the cable to the G-PON SFP port of the
LIM-GP4P module and the optical splitter. The optical splitter can be connected to the
maximum number of 64 ONT (Optical Network Terminal).
LIM-GP4P
ONT
The Corecess S5 System can manage the following tasks through local or remote connection.
Can browse various network statistics information and the status of the switch and ports.
Can change the switch configuration for changing the topology, improving the switch
performance or controlling the network traffic.
Can browse the logs of various events and traps occurring at the switch.
Can strengthen the system security through specifying hosts that can access switches.
This section describes how to connect the console port and the Ethernet management port to the
console terminal and the Ethernet LAN.
Installation 3-15
Connecting the System Management Device
SCM-B208G
Note: Connecting the Console port on the SCM is the same, regardless of the Corecess
chassis type. This manual describes system installation based on the Corecess S5 chassis .
SCM-B208G
Note: The Ethernet Management port in the SCM module support automatic MDIX feature,
which allows you to use either straight-through or crossover twisted-pair cables for
connecting to any network devices.
Note: Connecting the Ethernet Management port on the SCM is the same, regardless of the
Corecess chassis type. This manual describes system installation based on the Corecess
S5 chassis.
Installation 3-17
Connecting Power
Connecting Power
There two connecting power type of the Corecess S5 System. The Corecess S5 chassis can be
connected with DC power. The Corecess S5 chassis, on the other hand, can be connected with
AC power. This section describes how to connect power to the Corecess S5 System.
Connecting DC Power
There are two or three terminal blocks in the Corecess S5. If you want to use power redundancy
function, connect each terminal block to the different external power supply. If you connect
only one terminal block to the external power supply, the power redundancy function is
disabled.
1. For safety, a transparent plastic cover is attached on the terminal block. Loosen the two
screws using a screw driver, and remove the plastic cover.
Plastic Cover
Plastic Cover
2. Connect the DC power cable to the terminal block A. Loosen the screws from the terminal
block A, and put the rounded rope of the power cable, then tighten the screws again. Be
aware of power polarity when connecting cables. Attach the transparent plastic cover on
the terminal block A again.
Plastic Cover
3. Connect the DC power cable, connected with the terminal block A, to the external power
supply or the rectifier.
Installation 3-19
Connecting Power
4. Connect the DC power cable to the terminal block B. Loosen the screws from the terminal
block B, and put the rounded rope of the power cable, then tighten the screws again. Be
aware of power polarity when connecting cables. Attach the transparent plastic cover on
the terminal block B again.
Plastic Cover
5. Connect the DC power cable, connected with the terminal block B, to the
external power supply or the rectifier. For the power redundancy, the DC power cable
should be connected to the different external power supply from what connected to the
terminal block A.
Connecting AC Power
There are two power modules in front of the Corecess S5. If you want to use power redundancy
function, connect each terminal block to the different external power supply. If you connect
only one terminal block to the external power supply, the power redundancy function is
disabled.
1. Be sure that the power switch on the power module is turned off.
2. Connect the power cable, which is provided with the Corecess S5 System, to the power
input on the power module. Then, plug opposite side of the power cable into an outlet.
AC Power
Installation 3-21
Starting the System
1. Check the followings once again before operating the Corecess S5 System:
Make sure that modules are properly inserted in the slot of the Corecess S5 System.
2. Turn on the power of the console terminal and execute the terminal emulator
program.
3. Supply power to the Corecess S5 System. In case of the Corecess S5, turn on the
switches of the external power supplies. In case of the Corecess S5, turn on the switches of
the power modules on the Corecess S5 System.
5. If the power is properly supplied to the Corecess S5 System without any problem, the RUN
LED turns on in green, and the following message is displayed on the console terminal.
6. Once the initialization is properly completed in a short while, the RUN LED is
starting to flash green. And the following login message is displayed on the console screen.
Localhost login:
Now, the Corecess S5 System is properly installed. Log in the CLI of the Corecess system, then
configure the system depend on the environment of site.
Installation 3-23
Edition: 0006
Distribution: 12/2012
This chapter briefs general configuration method of the Corecess S5. The Corecess S5 has already
configured with default upon the shipment and can immediately be used without additional configuration
explained in this chapter. If the default configuration should be changed according to user’s network
environment, refer to the contents in this chapter.
Before Configuration
Before Configuration
This section describes how to access the Corecess S5 System CLI (Command Line Interface) and
provides information that you should know before using the Corecess S5 System CLI.
5. To access the Corecess CLI on the console screen, the console port on the Corecess S5
System should be connected to a serial port(DB-9) of the console using a console cable as
the following figure:
SCM-B208G
6. Make sure that you have started the emulation software program such as HyperTerminal
from your console terminal.
7. Press [Enter], then the following login message is displayed on the console terminal:
login:
8. Enter the login ID and the password, then press the [Enter]. The default login id is
‘corecess’. If you entered the login ID and the password correctly, localhost> prompt
appears.
Login: corecess
Password:
localhost>
9. To configure the Corecess S5, enter the ‘Privileged’ mode by enable command. If you
enter Privileged mode, the prompt is changed from localhost> to localhost#.
Localhost> enable
localhost#
Note: After specifying the IP address of the NMS port (Management interface), you can
access the Corecess S5 CLI through the Telnet session or NMS.
Command Modes
The CLI of the Corecess S5 System supports various command modes. The CLI commands are
only executed in their command modes. The following table describes the type of command
modes and the tasks.
You can enter the each command mode by entering the following command.
When you start a session on the Corecess S5, you begin in User mode. Only a limited subset of
the commands is available in User mode. To have access to all commands, you must enter
Privileged mode. To enter Privileged mode from User mode, enter the enable command. The
CLI prompt will be changed from > to # entering Privileged mode.
Localhost> enable
localhost#
To exit from Privileged mode, enter disable command. The CLI prompt will be changed from #
to > returning to User mode from Privileged mode.
Localhost# disable
localhost>
If you enter the exit command in Privileged mode, you can exit from the CLI.
Localhost# exit
login:
Global configuration mode allows you to change configuration for the Corecess S5 System. Also,
you can enter other configuration mode through Global configuration mode.
To enter Global configuration mode from Privileged mode, enter the configure terminal
command. The CLI prompt will be changed localhost(config)# entering Global configuration
mode.
To exit from Global configuration mode, enter end command. The CLI prompt will be changed
to localhost# returning to Privileged mode.
Localhost(config)# end
localhost#
This example shows how to return to Privileged mode from Policy-map mode by using the
exit command:
localhost(config-pmap)# exit
localhost(config-qos)# exit
localhost(config)# exit
localhost#
To return to Privileged mode directly without what mode you are in, use the end command.
This example shows how to return to Privileged mode from Policy-map mode by using the end
command:
localhost(config-pmap)# end
localhost#
To log out from the CLI, enter the exit command in User mode or Privileged mode.
This example shows how to log out from the CLI in Privileged mode. After logging out from
the CLI, login prompt will be displayed as follow.
Localhost# exit
login:
Prompt
On the Corecess S5 CLI prompt, the node name and current command mode are indicated as
follows:
localhost(config-qos)#
Node name Command mode
Node Name
The default node name is ‘localhost’. This default node name is used for the prompt until you
change it. If the proper node name is specified, it is useful to classify the product purpose or the
location.
Note: You can change the node name of the Corecess S5 System by using hostname
command in global configuration mode.
The following table describes the prompt of the main command modes.
Getting Help
The Corecess S5 CLI provides help system that shows the list of available commands or
parameters. You can also get information about their function and brief Description of usage.
To obtain a list of commands that are available for each command mode, enter a question
mark (?) at the prompt:
# ?
calendar calendar
clear Reset functions
clock System clock
close Close the terminal
cls Clear a screen
configure Configuration from vty interface
copy Copy from one file to another
debug
delete Delete
diag Diagnosis mode
disable Turn off privileged mode command
enable enable
end End current mode and down to previous mode
exit Exit current mode and down to previous mode
help Description of the interactive help system
list Print command list
no Negate a command or set its defaults
ping send echo messages
quit Exit current mode and down to previous mode
reset reset
session Create Session
show Show
ssh Open a ssh connection
telnet Open a telnet connection
terminal Set terminal line parameters
traceroute Trace route to destination
undebug Disable debugging functions (see also ‘debug’)
update Update Images
write Write Information
#
To obtain the syntax for commands that are available for each command mode, enter the
list command at the prompt:
# list
calendar set WORD [WORD] [WORD] [WORD]
clear arp
clear arp A.B.C.D
clear arp-cache
clear dhcp statistics
clear dhcprelay lease all
clear dhcpserver lease all
clear dhcpserver lease ip A.B.C.D
clear dhcpserver lease mac A:B:C:D:E:F
.
.
update option image NAME slot <1-100>
update option image id <1-100> slot <1-100>
update port epon WORD onu mac WORD image NAME
update rootfs image NAME
update rootfs image id <1-100>
write dhcpserver leasefile
write file
write memory
write terminal
#
To obtain a list of any command’s associated keywords and arguments, enter a question
mark (?) after a partial command followed by a space:
# clear ip ?
bgp BGP information
dhcp Dynamic Host Configuration Protocol
igmp Internet Group Management Protocol
mroute Delete multicast route table entries
ospf OSPF information
pim Protocol Independent Multicast (PIM)
prefix-list Build a prefix list
rip RIP routing table
route all routing table
static Static routing table & configuration
vrrp VRRP information
# clear ip
The CLI supports command completion, so you do not need to enter the entire name of a
command or parameter. As long as you enter enough characters of the command or
parameter to avoid ambiguity with other commands or parameters, the CLI understands
what you are typing. For example, you can enter only con t to execute the configure
terminal command at Privileged command mode.
Localhost# con t
localhost(config)#
But if you enter only co t, the following error message will be displayed. Because there are
copy and configure command and the system can’t distinguish the two commands.
Localhost# co t
% Unknown command.
To complete a command, press Tab key. If you enter a few known characters, then press Tab
key, the CLI displays the rest characters of the command. For example, if you enter only con
in Privileged mode, then press Tab key, the CLI displays configure on the terminal.
Specifying Ports
Use slot-number/port-number to specify one port. For example, enter 1/1 to specify the port 1
on the module installed in the slot 1.
Use dash (-) to specify consecutive number of ports. For example, enter 1/1-4 instead of
entering 1/1, 1/2, 1/3 and 1/4.
Use comma (,) to specify non-consecutive number of ports. For example, enter 1/1,1/3-4
instead of entering 1/1, 1/3 and 1/4.
Editing Commands
The CLI supports the following line editing commands. To enter a line-editing command, use
the CTRL-key combination for the command by pressing and holding the CTRL key, then
pressing the letter associated with the command.
To set the IP address of the Ethernet management port, follow this procedure:
Command Description
enable 1. Enter Privileged mode.
Configure terminal 2. Enter Global configuration mode.
Interface 3. Enter Interface configuration mode for configuring the Ethernet management
management port.
10. Assign an IP address and subnet mask to the Ethernet
Ip address management port.
<ip-address>/<M> <ip-address>: IP address for the interface.
<M>: Subnet mask.
5. Exit from Interface configuration mode and return to Global configuration
Exit
mode.
Ip route default 11. Specify the default gateway address.
<gateway-address> <default-gateway>: Default gateway address.
End 7. Return to Privileged mode.
Show interface
8. Verify the IP address configuration.
management
12. Check the network connectivity.
Ping <host>
<host>: The IP address of the host or the network number to ping.
Write memory 10. Save the IP address configuration.
The following is an example of assigning an IP address and subnet mask to the Ethernet
management port and verifying the configuration:
(config)# interface management Enter the interface mode of the Ethernet Manegement port
Specify the IP address and subnet mask of
(config-if)# ip address 172.27.68.100/16
the Ethernet Management port
(config-if)# exit Enter the Global Configuration Mode
172.27.2.49 is alive!
# write memory Save the changed configuration to the backup configuration file
Building Configuration…
[OK]
#
User Management
To access the CLI of the Corecess S5 System, you must login by entering the user name and the
password. By default, ‘corecess’ exists. This section describes how to add and delete user who
can login the CLI of the Corecess S5 System.
Command Description
enable 1. Enter Privileged mode.
The following example shows how to adds a user whose id is ‘kka’ and password is ‘violet’ and
verifies the configuration:
# configure terminal
(config)# username kka passwd violet
(config)# end
# show username
corecess none none **Never logged in**
kka none none **Never logged in**
# write memory
Building Configuration…
[OK]
Command Description
The following example shows how to change a password of the user ‘kka’:
# configure terminal
(config)# user kka password corecess
(config)# end
# write memory
Building Configuration…
[OK]
#
Deleting a User
Command Description
The following example shows how to delete the user ‘kka’ and verify the deletion:
# configure terminal
(config)# no username kka
(config)# end
# show username
corecess none none **Never logged in**
# write memory
Building Configuration…
[OK]
#
System name
System date and time
NTP (Network Time Protocol) mode and time zone
Time zone
The system name is used as the prompt on the console. Therefore, it is convenient for finding
out which device is connected to. To change the system name, use the following commands.
Command Description
The following example shows how to change the system name to ‘Corecess’:
localhost> enable
localhost# configure terminal
localhost(config)# hostname Corecess
Corecess(config)# end
Corecess# write memory
Building Configuration…
[OK]
Corecess#
The system date and time is used in the log which is the record of the events occurred in the
system. When recording events or commands executed in the system into a log, the date and
time of the system is recorded with events or commands. Such logs can be used as an important
data in solving problems in the system, thus it is very important to accurately set the date and
time of the system.
The following describes how to set the system time and date.
Command Description
The following example shows how to adjust the system calendar and change the system clock
into the system calendar:
# clock set 33:20:10 8 mar 2004
# show clock
Fri Oct 8 17:37:49 2004 -0.066680 seconds
# write memory
Building Configuration…
[OK]
To use the current software clock (calendar) as the system clock, use the clock read-
calendar command in Privileged mode.
# show calendar
Fri Oct 8 11:26:38 KST 2004
# clock read-calendar
# show clock
Fri Oct 8 11:26:38 2004 -0.440000 seconds
Note: The ‘calendar’ is a software clock that is erased when the system is powered off or
reboot. The other hand, the system clock run continuously, even if the system is powered off
or reboot.
NTP (Network Time Protocol) synchronizes timekeeping among a set of distributed time
servers and clients. This synchronization allows events to be correlated when system logs are
created and other time-specific events occur.
The Corecess S5 supports the following NTP modes:
Broadcast client mode
In broadcast client mode, local network equipment, such as a router, regularly broadcasts the
time information. The Corecess S5 System listens for the broadcast messages and set the
system clock.
Server mode
In server mode, the Corecess S5 System regularly requests the time information to an NTP
server.
To configure NTP on the system, use the following commands:
Command Description
The following example shows how to configure the system in NTP server mode and verify the
configuration:
You can specify a time zone for the Corecess S5 System to display the time based on that time
zone. The Corecess S5 System learnt time from NTP sets its clock according to the specified time
zone and displays time. For example, when you set the time zone as ‘Seoul’ and ‘Los Angeles’,
the displayed date is different.
The default time zone is UTC. You must enable NTP before you set the time zone. If NTP is not
enabled, this command has no effect.
Command Description
configure terminal 1. Enter Global configuration mode.
19. Set the time zone.
<region>: The region name. Select one of followings:
4-21thern Africa region
america America region
antarctica Antarctica region
arctic Arctic region
asia Asia region
atlantic Atlantic region
4-21thernet4-21 Australia region
4-21thern Europe region
Clock timezone
indian Indian region
<region> <area-code>
pacific Pacific region
cet CET(Central Europe time UTC+1)
eet EET(Eastern Europe Time UTC+2)
est EST(Estern Standard Time UTC-5)
gmt GMT(Greenwich Mean Time UTC)
pst PST(Pacific Standard Time UTC-8)
utc UTC(Universal Time Clock)
<area-cded>: Area code(area code, 1 ~ 1000). You can see the
area code for the selected region by using the show clock
timezone <region> in Privileged mode.
The following example shows how to set the time zone and the area code to Asia/Seoul:
The Corecess S5 System contains two types of configuration files: the running (current
operating) configuration and the startup (last saved) configuration.
The feature of the files is as follows:
Running configuration
The running configuration is the current (unsaved) configuration that reflects the most recent
configuration changes. When a user changes the system configuration, the system configuration
is saved in the running configuration file of RAM and is applied immediately to the system.
You can upload or download the running configuration file via FTP or TFTP.
Startup configuration
The startup configuration is the saved configuration in NVRAM and is used when the system
initializes. The startup configuration is not removed when the system power is turned off. You
can upload or download the startup configuration file via FTP or TFTP.
Caution: Whenever you make changes to the Corecess S5 System configuration, you must
save the changes to memory so they will not be lost if the system is rebooted.
Command Description
The following example shows how to display the current running configuration file of the
Corecess S5 System.
# show running-config
Building configuration…
Current configuration:
!
! version 0.73
!
hostname Corecess
!
snmp-server community “public” ro
snmp-server community “private” rw
snmp-server contact Unknown
snmp-server location Unknown
snmp-server enable rmon
!
system fan enable 33 25
system temperature enable 90 80
!
port gigabitethernet 1/1 flowctl off
port gigabitethernet 1/1 duplex full
port gigabitethernet 1/2 flowctl off
port gigabitethernet 1/2 duplex full
port gigabitethernet 1/3 flowctl off
port gigabitethernet 1/3 duplex full
port gigabitethernet 1/4 flowctl off
port gigabitethernet 1/4 duplex full
!
interface management
ip address 172.18.22.6/16
!
ip multipath count 32
!
line vty
!
dhcprelay enable
dhcprelay serverlist 100.1.1.1
!
no ntp
!
.
.
#
There are three commands to save the current running configuration file to the startup
configuration file.
Command Mode
write memory
The following example shows how to save the current running configuration to the startup
configuration using the write memory command:
# write memory
Building Configuration…
[OK]
#
The following example shows how to save the current running configuration to the startup
configuration using the write file command:
# write file
Building Configuration…
[OK]
#
The following example shows how to save the current running configuration file to the startup
configuration file using the copy running-config startup-config command.
Command Description
Copy factory-default
2. Restore the default configuration.
start-up config
To check whether the Corecess S5 System is properly connected and configured, use the
following commands:
Commands Description
enable 1. Enter Privileged mode.
20. Ping another node on the network.
<destination>: The IP address of the host or the network
Ping <destination>
number to ping.
[count <packet-count>]
count: Sends the specified number of ICMP packets.
- <packet-count>: The number of packets to send (1 ~ 512).
21. Trace the route of packets through the network to another
Traceroute [<host-ip> node.
| <host-name>] <host-ip>: Destination address.
<host-name>: Host name.
show interface 4. If the host is unresponsive, check the IP address and the subnet mask
management in the configuration of the Ethernet Management port.
5. If the interface of the Ethernet Management port is properly
Show ip route
configured, check the IP routing table.
# ping 172.27.2.49
PING 172.27.2.49 (172.27.2.49) from 172.27.2.100 : 56(84) bytes of data.
64 bytes from 172.27.2.49: icmp_seq=0 ttl=128 time=955 usec
64 bytes from 172.27.2.49: icmp_seq=1 ttl=128 time=817 usec
64 bytes from 172.27.2.49: icmp_seq=2 ttl=128 time=816 usec
64 bytes from 172.27.2.49: icmp_seq=3 ttl=128 time=8.284 msec
64 bytes from 172.27.2.49: icmp_seq=4 ttl=128 time=820 usec
The following messages are displayed according to the status of host and network after
execution of the ping command:
64 bytes from <host> : Host or network is connected. (When the ICMP echo response
icmp_seq=n ttl=n time=n ms messages have been received from the host or network)
Destination does not respond. (When any packets have not
no answer from <host>
been received from the host or network)
<host> is unreachable Host is unreachable.
This example shows how to perform a traceroute to the host whose IP address is 192.1.1.1:
# traceroute 192.1.1.1
traceroute to 192.1.1.1 (192.1.1.1), 30 hops max, 38 byte packets
22. * 172.27.1.254 (172.27.1.254) 4.204 ms 9.754 ms
2 * 192.168.11.126 (192.168.11.126) 1.640 ms 1.317 ms
3 61.107.96.1 (61.107.96.1) 1.825 ms 1.778 ms 1.441 ms
4 61.96.195.249 (61.96.195.249) 1.723 ms 1.812 ms 1.838 ms
5 172.30.4.1 (172.30.4.1) 2.375 ms 1.838 ms 1.856 ms
6 172.30.100.33 (172.30.100.33) 2.212 ms 1.813 ms 1.838 ms
7 172.30.100.10 (172.30.100.10) 2.404 ms 1.888 ms 2.277 ms
8 211.61.251.1 (211.61.251.1) 2.305 ms 1.861 ms 1.802 ms
9 211.61.251.4 (211.61.251.4) 3.338 ms 2.812 ms 2.811 ms
.
.
.
19 4.0.2.250 (4.0.2.250) 218.205 ms 4.1.81.1 (4.1.81.1) 220.789 ms *
20 4.1.138.38 (4.1.138.38) 220.070 ms 227.188 ms 4.1.81.1 (4.1.81.1) 23.769
ms
21 4.1.138.38 (4.1.138.38) 219.686 ms 192.1.101.81 (192.1.101.81) 222.896 ms
4.1.138.38 (4.1.138.38) 220.625 ms
22 * 192.1.101.81 (192.1.101.81) 219.597 ms 218.852 ms
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
The following example displays sample traceroute output when a destination host IP
address is specified:
# traceroute 61.107.97.51
traceroute to 61.107.97.51 (61.107.97.51), 30 hops max, 40 byte packets
1 172.26.1.254 (172.26.1.254) 14.812 ms 29.758 ms 22.752 ms
2 192.168.11.126 (192.168.11.126) 0.497 ms 0.454 ms 0.360 ms
3 61.107.97.51 (61.107.97.51) 14.812 ms 29.758 ms 22.752 ms
#
The table below describes the fields shown by the traceroute command:
Field Description
Maximum TTL value and the size of the ICMP datagrams being sent
Indicates the sequence number of the switch router in the path to the host
IP address of the router
Round-trip time for each of the three probes that are sent
If the host is irresponsible after execution of the PING or traceroute commands, check the
interface of the Ethernet Management port using the show interface management
command, and check the routing table using the show ip route command.
The following example shows how to display the interface of the Ethernet Management port
using the show interface management command.
The following example shows how to display the IP routing table using the show ip route
command.
# show ip route
Codes: K – kernel route, C – connected, S – static, R – RIP, O – OSPF,
I – IS-IS, B – BGP, > - selected route, * - FIB route, p – stale info
# show cpuinfo
cpu : 440GP Rev. C
revision : 4.129 (pvr 4012 0481)
bogomips : 595.96
vendor : IBM
machine : Ebony
#
The following table describes the fields shown by show cpuinfo command:
Field Description
Bogomips is the number of million times per second a CPU can do absolutely nothing
Bogomips
and is used for a measurement of speed for the non Intel CPUs.
The following example shows how to display the information of the memory.
# show meminfo
total: used: free: shared: buffers: cached:
Mem: 250851328 106090496 144760832 0 3883008 40488960
Swap: 0 0 0
MemTotal: 244972 kB
MemFree: 141368 kB
MemShared: 0 kB
Buffers: 3792 kB
Cached: 39540 kB
SwapCached: 0 kB
Active: 8684 kB
Inactive: 77488 kB
HighTotal: 0 kB
HighFree: 0 kB
LowTotal: 244972 kB
LowFree: 141368 kB
SwapTotal: 0 kB
SwapFree: 0 kB
#
The table below describes the fields shown by the show meminfo command:
Field Description
(Continued)
Field Description
# show module
Codes : * - Internal/Built-in Module, N – Network Attached Module
X – Switch Fabric Module, > - Current Management Module
Module Ports Description Status Serial No.
------- ----- ------------------------------- ---------------- -------------
> A(S1) N/A Control Module active N/A
B(S2) N/A Control Module not-exist N/A
1 16 S5-LIM-GW16 insert,up N/A
2 N/A N/A not-exist N/A
3 N/A N/A not-exist N/A
4 4 S5-EP8G-2.5 insert,up N/A
5 N/A N/A not-exist N/A
6 N/A N/A not-exist N/A
7 N/A N/A not-exist N/A
8 N/A N/A not-exist N/A
* 17 4 UIM-4GTX insert,up N/A
* 18 4 UIM-4G(SCM-B208G) insert,up N/A
X 19 64 FABRIC-B208G insert,up N/A
Module Version Hw Fw Sw
------- ------------------ ---------------- --------------- ---------------
1 release.rev(patch) N/A 1.0(18) N/A
4 release.rev(patch) 0.0(3) 1.0(177) REL0.6.6RC2
17 release.rev(patch) N/A N/A N/A
18 release.rev(patch) 0.0(1) N/A N/A
19 release.rev(patch) N/A N/A N/A
The table below describes the fields shown by the show module command:
Field Description
# show system
System Information
CoreCMR(Control Module Redundancy)
side : A(M2)
local status : active
remote status : not-exist
mode : hot-startup
PWR [ 1] Unequipped
PWR [ 2] Unequipped
PWR [ 3] Unequipped
FAN [ 1] Normal
FAN [ 2] Normal
Auxiliary Information
Fan (`C(`F)) –
Max/Min Threshold : 33/ 25 ( 91/ 77)
Temperature (`C(`F)) –
Current Temperature : 53 (127 )
Max/Min Threshold : 90/ 80 (194/176)
MIB-II: System Group
Contact: support@corecess.com
Name: Corecess S5
Location: Corecess Inc.
Descr: Switched Router
ObjectID(36): 1,3,6,1,4,1,2971,50,45
Each field shown by the show system command describes the following information about
system state:
Field Description
CoreCMR The redundancy status of the SCM module (Not supported).
The status of the SCM module and the LIM module.
SIB S [1] : The status of LIM module installed in the number 1 slot
SIB S [2] : The status of LIM module installed in the number 2 slot
SIB S [3] : The status of LIM module installed in the number 3 slot
System Subscriber/Service SIB S [4] : The status of LIM module installed in the number 4 slot
Information Interface Board(s)
SIB S [19] : The status of SCM module installed in the number 5 slot
FAN The status of the fan module
Max Threshold : The temperature that the fan module operate
Fan
Min Threshold : The temperature that the fan module stop
Auxiliary Current Temperature : The current temperature of the Corecess S5
Information System
Temperature
Max Threshold : The maximum temperature that the trap occurs
Min Threshold : The minimum temperature that the trap occurs
Controling FAN
This CLI control automatic fan on/of based on temperature.
(config)#
system fan disable
system fan enable <Max Threshold> <Min Threshold>
By default, all events of the Corecess S5 System are specified to the level 6. Thus, if the event
occurs from the level 1 to the level 6, the event message is displayed on the console screen or
the remote host screen.
The event level can be changed. The following procedure describes how to change the event
level.
Command Description
This example shows how to specify the sys event to the level 4 and verify the result.
# configure terminal
(config) # logging level sys 4
(config) # end
# show logging
console logging is disable
logging buffer is disable
# write memory
Building Configuration…
[OK]
#
Event Description
sys Events related to system hardware
filesys Events related to file system
authorize Events related to security and authentication
port Events related to ports
interface Events related to interfaces
vlan Events related to VLAN (Virtual LAN)
spantree Events related to spanning tree and bridge
lacp Events related to LACP (Link aggregation Control Protocol)
gvrp Events related to GARP/GVRP
igmp Events related to IGMP and IGMP snoopping
pbnac Events related to PBNAC (Port Base Network Access Control)
mcast Events related to multicast
qos Events related to QoS (Quality Of Service)
acl Events related to access list
snmp Events related to SNMP
snmp_rmon Events related to SNMP RMON
dhcp Events related to DHCP
ntp Events related to NTP
route_main Events related to Main Routing Control
rip Events related to RIP
ospf Events related to OSPF
bgp Events related to BGP
dvmrp Events related to DVMRP
pim Events related to PIM
To configure the log messages to display on the console screen, use the following commands:
Command Description
The following example configures the log messages to display on the console screen and check
the result:
# configure terminal
(config)# logging console enable
(config)# end
# show logging
console logging is enable
logging buffer is enable
logging servers
1.1.1.1
.
.
# write memory
Building Configuration…
[OK]
#
To configure the log messages to display on a remote host, use the following command:
Command Description
The following example configures the system log to display on the remote host whose IP
address is 172.10.1.0:
# configure terminal
(config)# logging 172.10.1.0
(config)# end
# show logging
console logging is enable
logging buffer is enable
logging servers
172.10.1.0
.
.
# write memory
Building Configuration…
[OK]
#
To configure the log messages to display on telnet sessions, use the following commands:
Command Description
The following example configures the system log to display on telnet sessions:
# configure terminal
(config)# logging session enable
(config)# end
# write memory
Building Configuration…
[OK]
#
The following example shows how to configure the log message to be save in a file:
# configure terminal
(config)# logging file enable
(config)#
The following table describes the fields shown by the show logging buffer command:
No Description
Date and time that the event occurred (month, date, hour:minute:second)
System name
The brief Description of the event
Upgrading Software
Copy ftp(tftp)
You can download the software for the modules on the Corecess S5 System from a remote TFTP
or FTP server. To download software from a remote TFTP or FTP server to the Corecess S5
System, perform this task:
Command Description
enable 1. Enter Privileged mode.
Copy {tftp <host-ip> | 27. Download specified file from the TFTP or FTP server.
ftp <host-ip> [id <host-ip> IP address of the TFTP or FTP server
<login-id> passwd <login-id> Login ID of FTP server
<password>]} flash image <password> Login password of FTP server
<file-name>
<file-name> file name to download
show flash image 3. Verify software download.
28. Apply the download file to the system.
Update flash image id
<file-name> File name to apply
{<file-name> | <file-id>}
<file-id> File ID to apply
reset system 5. Reboot the system.
The following example shows how to download the image file from TFTP server and apply the
download file to the system.
# copy tftp 172.27.2.17 flash image hamster-base-osapp-epon.img
tftp: data 10000 Kbytes
# show flash image
System flash directory:
File Length (bytes) Name/status
----- --------------- -----------------------------------
1 6875913 cS5-base-osapp-REL1.0.1.img (*)
2 6266476 hamster-base-osapp-REL1.0.0.img
3 6317126 hamster-base-osapp-REL1.0.1.img
4 6226882 hamster-base-osapp-epon.img
[31208 blocks used, 27960 available, 59168 total, 1K-blocks]
*/# : running/updated image
# update flash image id 3
# reset system
PPCBoot 2.0.0 (Apr 16 2003 – 14:29:15)
Corecess Boot Ver 1.0 (Apr 16 2003 14:29:15)
Copy Flash
You can upload the image or 4-48thernet4-484-48ion file to a remote FTP(TFTP) server or in
flash memory of the system.
configuration
This chapter describes how to configure the Gigabit Ethernet port, the Gigabit PON port and ONU.
Configuring Gigabit Ethernet port
Trap Disabled
Whenever the port configuration is changed, the changed configuration is applied immediately
to the system without the system rebooting or the command execution. Yet, if you want to keep
using the configuration after the system rebooting, the changed configuration should be saved
using the write memory command in Privileged mode.
All ports of the Corecess S5 System are enabled by default. To change administrative status
(disabling a port or reenabling a port), use the following command in Global configuration
mode:
Command Description
The following example shows how to disable the Gigabit Ethernet port 17/1.
The following example shows how to reenable the Gigabit Ethernet port 17/1.
The auto sensing function of the Gigabit Ethernet port is used to exchange flow control
parameter, fault information of remote ports and transfer mode information. By default, the
auto sensing function is enabled on the Gigabit Ethernet port of the Corecess S5 System.
Ports that are located in both ends of the Gigabit Ethernet link must have the same
configuration. If the configurations are different each other, the link cannot be connected. The
following table shows connection state of link depending on state of the auto sensing function
on the Gigabit Ethernet port.
To enable the auto sensing function of the Gigabit Ethernet port, use the following command in
Global configuration mode.
Command Description
port gigabitethernet
<slot>/<port> <slot>/<port> slot number/port number
link-status auto
The following example shows how to enable the auto sensing function on the Gigabit Ethernet
17/1:
By default, the Gigabit Ethernet port on the Corecess S5 System can automatically match
transmission speed of the connected port. This function is called the auto-negotiation. The
maximum speed of the 10/100/1000Base-T port can be set as 10/100/1000Mbps by users
instead of auto-negotiation.
If the port speed is set as 10/100Mbps, full-duplex or half-duplex mode is operated. If the port
speed is set as 1000Mbps, only full-duplex is operated.
To change port speed and the transfer mode of the 10/100/1000Base-T port, use the following
commands.
Command Description
29. Set the port speed of the specified port.
<slot>/<port> Slot/Port number
<port-speed> Transfer speed of the specified port
port gigabitethernet
- 10 10Mbps
<slot>/<port> speed
- 100 100Mbps
<port-speed>
- 1000 1Gbps
- auto Auto-negotiation mode
- reset reset the auto-negotiation mode
The following example shows how to change port speed and the transfer mode of the
10/100/1000Base-T port on the SCM module (17/1).
You can enable or disable flow control of a port, which manages traffic rates during congestion.
If a port experiences congestion and cannot receive any traffic, flow control notifies the other
port to stop transmitting until the condition clears.
By default, flow control is disabled on the ports of the Corecess S5 System. To change flow
control status, use the following command in Global configuration mode:
Command Description
<slot>/<port> Port/Slot number
port gigabitethernet <status> Flow control status
<slot>/<port> - on Enables flow control
flowctl <status> - off Disable flow control
- auto Auto-negotiation
The following example enables flow control on the Gigabit Ethernet port 17/1:
You can assign a name to each port. If you use connected device information as port names, you
can manage the devices easily.
To set a port name, use the following command in Global configuration mode:
Command Description
port gigabitethernet
<slot>/<port> Slot/Port number
<slot>/<port>
<port-name> Port name (Maximum: 32 character)
name <port-name>
The following example shows how to set the name of the Gigabit Ethernet port 17/1.
When port status is changed (up, down), a SNMP link trap is occurred, then the SNMP agent
notifies SNMP host or NMS of the trap occurrence.
By default, the SNMP link trap of the ports on the Corecess S5 System is disabled.
To set trap for a port, use the following command in Global configuration mode:
Command Description
31. Enable or disable the SNMP link trap for the specified port.
<port-type>: The type of Ethernet port to configure.
port <port-type>
- fastethernet: Configures Fast Ethernet port.
<slot>/<port> trap
- gigabitethernet: Configures Gigabit Ethernet port.
link-status
<slot>: Slot number (1 ~ 2)
<port>: Port number (1 ~ 24)
The following example enables the SNMP link trap on the gigabitethernet port 17/1:
The following example show information of all port on the Corecess S5 System using the show
port command.
# show port
Port Name Status Vlan FlwCtl Duplex Speed Type
----- --------------- ---------- ----- ------ ------ ------------- ----------
1/1 DEFAULT connected 1 off full 1000 1000BaseT
1/2 DEFAULT connected 1 off full 1000 1000BaseT
1/3 DEFAULT connected 1 off full 1000 1000BaseT
1/4 DEFAULT connected 1 off full 1000 1000BaseT
.
.
17/1 DEFAULT connected 1 a-on a-full a-1000 1000BaseT
17/2 DEFAULT connected 1 a-on a-full a-1000 1000BaseT
17/3 DEFAULT connected 1 a-on a-full a-1000 1000BaseT
17/4 DEFAULT connected 1 a-on a-full a-1000 1000BaseT
#
The table below describes the fields shown by the show port command:
Field Description
The following example show information of the Gigabit Ethernet port 17/1 using the show
port command.
If Index Logical ID
---------- ----------
4 257
access-type : transparent
Extension status
#
The table below describes the fields shown by the show port command with a port number:
Field Description
AdminStatus Admin status of the port (enable, disable).
Media-type Media type(MDI/MDIX) of the port (none).
STP STP status of the port (enable, disable).
RSTP Edge RSTP status of the port (enable, disable).
(Continued)
Field Description
Trap Whether to enable displaying trap messages of the port (enable, disable).
LinkAgg. LACP status of the port (on, off).
Admin Speed Maximum speed of the port.
Limited Speed Limited speed of the port.
Active Speed Current speed of the port.
If Index Interface number of the port.
Logical ID Logical ID of the port.
All Total number of the incoming/outgoing packets on the port.
Port Unicast Total number of the incoming/outgoing unicast packets on the port.
Statistics Multicast Total number of the incoming/outgoing multicast packets on the port.
Counters Broadcast Total number of the incoming/outgoing broadcast packets on the port.
(in/out) Discard Number of the incoming/outgoing packets discarded on the port.
Error Number of the incoming/outgoing packets with errors on the port.
input runt Number of packet less than 64 byte without CRC error.
shortCRC Number of packet less than 64 byte with CRC error.
normalCRC Number of packet with CRC error
Number of incomplete packet that is not divided by eight with CRC
normalAlign
error.
longCRC Number of packet less than 1518 byte with CRC error
Port Error
output
Counters Number of packet that was not transmitted in the specified time.
defered
- single : Number of packet whose collision occurred once
- multi : Number of packet whose several collision occurred
Collision - consecutive : Number of packet whose collision occurred continuously
- late : Number of packet whose collision is not checked in the specified
time
LIM
ONU port(ONU
Item (LINE Interface LIM 1 Port Index(ONU)
Profile)
Module)
Max 64 Index, Serial
Specification GPON 2.5G Uni port, GEM port
number
port gpon
port gpon gpon-onu-profile
CLI pattern port gpon slot/port onu
slot/port NAME
index WORD
Whenever the port configuration is changed, the changed configuration is applied to the system
without the system rebooting or the command execution. But, if you want to keep using the
configuration after the system rebooting, the changed configuration should be saved using the
write memory command in Privileged mode.
Reset GPON
Note: It is prevented that direct comunicationon bwtween ONTs on the same PON port.
To allow that, one of the follow things is needed:
- Enable l2-port bridge on the port
- Use L3 redirection feature using proxy arp.
Whenever the port configuration is changed, the changed configuration is applied to the system
without the system rebooting or the command execution. But if you want to keep using the
configuration after the system rebooting, the changed configuration should be saved using the
write memory command in Privileged mode.
Argument Description
mtu mtu size
access-type Set access-type
admin Admin Status
bwlimit bandwidth limit
dscp dscp function
l2-port-bridge Allow the port to transmit the packet received from the port
l2-protocol l2-protocol handling
mac-security-sticky block mac-move, if mac is router mac
name Set name
pass-through Transparent Switching
perf-monitor Performance Monitoring
promiscuous Promiscuous Mode: All other ports become isolated
trap Set Trap
trust-mode Set Trust-Mode
tx-queue transmit queue
wred weighted random early detection
bridge-edge-
Set Bridge Edge Assumption
assumption
mirror mirroring
pathcost Set bridge path-cost
priority Set bridge priority
self-loop-detection Self Loop Detection
stp Set STP
authentication Authentication
fec Setting FEC mode configuration
onu ONU/ONT
onu-index-mode onu index mode
rg Residential Gateway
serial-number Serial number configuration
acs Auto Configuration Server
cir Maximum committed bandwidth allowed
cbs Maximum committed burst size allowed
pir Maximum excessive bandwidth allowed
pbs Maximum excessive burst size allowed
tengigabitethernet|gpon|adsl|vdsl|shdsl)
WORD perf-monitor
[en] show port
(fastethernet|gigabitethernet|epon|gpon|
Showing port-queue
tengigabitethernet|gpon|adsl|vdsl|shdsl)
WORD port-queue
[en] show port
(fastethernet|gigabitethernet|epon|gpon|
Showing wred
tengigabitethernet|gpon|adsl|vdsl|shdsl)
WORD wred
[en] show port
(fastethernet|gigabitethernet|epon|gpon| Showing port status
tengigabitethernet|gpon|adsl|vdsl|shdsl|
switchfabric|stacking) WORD
[en] show port
(fastethernet|gigabitethernet|epon|gpon|
Showing sfp module status
tengigabitethernet|gpon|adsl|vdsl|shdsl|
switchfabric|stacking) WORD sfp
[en] show port gpon WORD authentication Showing authentication status
[en] show port gpon WORD onu-service-
Showing onu service mode
mode
[en] show port gpon WORD gem-port Showing gpon port’s all gem port status
[en] show port gpon WORD gem-port vlan Showing gpon port’s all gem port vlan
uplink uplink config status
[en] show port gpon WORD gem-port- Showing ratelimit of GEM port
downstream-ratelimit downstream.
[en] show port gpon WORD broadcast-port
Showing ratelimit of broadcast GEM port.
ratelimit
[en] show port gpon WORD multicast-port Showing gpon port’s multicast gem port
[en] show port gpon WORD multicast-port
Showing ratelimit of multicast GEM port.
ratelimit
[en] show port gpon WORD redundancy Showing gpon port protection config of
port-configuration GPON port in PMC Chip.
Argument Description
profile GPON Profile
agingtime Mac aging time
allow Enabling onu access
igmp-snoop IGMP snoop
ip-host IP Host config data
port ONT user port
startup-config ONU switching device startup-config
static Setting ONU serial number to static
vlan Vlan Configuration
voip voip
aaa Authentication
port : Port
gpon :Gigabit PON port type
WORD : Port(s) ranges (ex. 1/1-2,2/4)
port gpon WORD onus-range min-
onus-range : Setting channel onus range of
config distance <0-60000> max-distance
distance
<0-60000>
min-distance : Set minimal distance of
onus in meter<0~60000>
max-distance : Set maximal distance of
onus in meter<0~60000>
Argument Description
aes-encryption AES encryption
bridge MAC Bridge
broadcast-gem-port Broadcast GEM port
clear clear
default default ONU/ONT profile
down-queue Downstream Queue
end End current mode and down to previous mode
equipment-id equipment-id of ONU/ONT
exit Exit current mode and down to previous mode
fec forward error correction
gem-port GEM port
igmp igmp
ip-host IP Host config data (134)
list Print command list
multicast-gem-port Multicast GEM port
no Negate a command or set its defaults
service-model service-model
service-model-file ONU configuration pre-profile for ONU Service Model
tcont T-CONT
uni-port uni port
up-queue Downstream Queue
voip voip
upstream :
Upstream frame is sent with
as-is : As is
downstream :
Downstream frame is sent with
as-is : As is
strip-tag :
Strip tag, if tag presents
Setting uni-port’s vlan tagging
operation config data
uni-port : UNI port
PORT_NUM : port number
(ex: 1 or 1,2 or 1,2,3-4)
tag : 802.1q Vlan using VTOCD
upstream :
uni-port PORT_NUM tag upstream Upstream frame is sent with
gpon-onu-
prepend-tag <1-4094> prepend-tag : Prepend tag, making
profile
downstream (as-is|strip-tag) untagged(tagged) into
tagged(double-tagged)
<1-4094> : Vlan tag id value
downstream :
Downstream frame is sent with
as-is : As is
strip-tag :
Strip tag, if tag presents
Setting uni-port’s vlan tagging
operation config data
uni-port : UNI port
PORT_NUM : port number
uni-port PORT_NUM tag upstream (ex: 1 or 1,2 or 1,2,3-4)
gpon-onu- prepend-tag <1-4094> priority tag : 802.1q Vlan using VTOCD
profile <0-7> downstream (as-is|strip- upstream :
tag) Upstream frame is sent with
prepend-tag : Prepend tag, making
untagged(tagged) into
tagged(double-tagged)
<1-4094> : Vlan tag id value
unauthenticated :
Force reauthentication
authenticated :
Force unauthenticated
Setting extended vlan tagging operation
of ONU user port
gpon-onu- uni-port : ONU user port
uni-port PORT_NUM extag
profile PORT_NUM : port number((ex : 1 or 1,2
or 1,2,3-4)
extag : 802.1q Vlan using EX-VTOCD
Setting extended vlan tagging operation
of ONU user port
uni-port : ONU user port
uni-port PORT_NUM PORT_NUM : port number((ex : 1 or 1,2
gpon-onu- extag (input-tpid| or 1,2,3-4)
profile output-tpid) extag : 802.1q Vlan using EX-VTOCD
<0-65535> input-tpid : Input TPID
output-tpid : Output TPID
<0-65535> : TPID value, Typical values
include 0x88a8 and 0x9100
Setting extended vlan tagging operation
of ONU user port
uni-port : ONU user port
PORT_NUM : port number((ex : 1 or 1,2
or 1,2,3-4)
extag : 802.1q Vlan using EX-VTOCD
uni-port PORT_NUM
double-tag : Double tagged frame
extag double-tag
<1-4094> : Outer tagged vid value
gpon-onu- <1-4094> <1-4094>
<1-4094> : Inner tagged vid value
profile add-tag <1-4094>
add-tag : Insert tag
(priority (<0-7>|9)
<1-4094> : 3rd Vlan tag vid value
(tp-id (0|1|2|3|4|6|7)))
priority : 3rd Vlan tag priority
tp-id : Treatment 3rd TPID/DE
0 : Copy TPID (and DE, if present) from
inner tag of received frame
1 : Copy TPID (and DE, if present) from
outer tag of received frame
or 1,2,3-4)
extag : 802.1q Vlan using EX-VTOCD
double-tag : Double tagged frame
<1-4094> : Outer tagged vid value
<1-4094> : Inner tagged vid value
swap-tag : Swap tag
Setting extended vlan tagging operation
of ONU user port
uni-port : ONU user port
PORT_NUM : port number((ex : 1 or 1,2
or 1,2,3-4)
uni-port PORT_NUM
gpon-onu- extag : 802.1q Vlan using EX-VTOCD
extag downstream-mode
profile downstream-mode : The downstream
(us-inverse|none)
mapping
none : No operation in downstream
us-inverse : The operation performed in
the DS is the inverse of that performed in
the US
Setting extended vlan tagging operation
of ONU user port
uni-port : ONU user port
PORT_NUM : port number((ex : 1 or 1,2
or 1,2,3-4)
extag : 802.1q Vlan using EX-VTOCD
single-tag : Single tagged frame
uni-port PORT_NUM <1-4094> : Tagged vid value
extag single-tag <1-4094> add-tag : Insert tag
gpon-onu-
add-tag <1-4094> <1-4094> : Vlan tag vid value
profile
(priority (<0-7>|8) priority : Vlan tag priority
(tp-id (0|2|4|6|7))) <0-7> : Vlan tag priority value
8 : Vlan tag priority from the inner
priority of the received frame
tp-id : Treatment TPID/DE
0 : Copy TPID (and DE, if present) from
inner tag of received frame
2 : Set TPID = output TPID attribute
value, copy DE bit from inner tag of
received frame
4 : Set TPID = 0x8100
6 : Set TPID = output TPID, DE=0
7 : Set TPID = output TPID, DE=1
Setting extended vlan tagging operation
of ONU user port
uni-port : ONU user port
PORT_NUM : port number((ex : 1 or 1,2
or 1,2,3-4)
extag : 802.1q Vlan using EX-VTOCD
single-tag : Single tagged frame
<1-4094> : Tagged vid value
change-tag : Change tag
uni-port PORT_NUM <1-4094> : Vlan tag vid value
extag single-tag <1-4094> priority : Vlan tag priority
gpon-onu-
change-tag <1-4094> <0-7> : Vlan tag priority value
profile
((priority (<0-7>|8) 8 : Vlan tag priority from the inner
(tp-id (0|2|4|6|7))) priority of the received frame
tp-id : Treatment TPID/DE
0 : Copy TPID (and DE, if present) from
inner tag of received frame
2 : Set TPID = output TPID attribute
value, copy DE bit from inner tag of
received frame
4 : Set TPID = 0x8100
6 : Set TPID = output TPID, DE=0
7 : Set TPID = output TPID, DE=1
Setting extended vlan tagging operation
of ONU user port
uni-port : ONU user port
uni-port PORT_NUM
PORT_NUM : port number((ex : 1 or 1,2
gpon-onu- extag single-tag <1-4094>
or 1,2,3-4)
profile change-tag <1-4094>
extag : 802.1q Vlan using EX-VTOCD
add-tag <1-4094>
single-tag : Single tagged frame
<1-4094> : Tagged vid value
change-tag : Change tag
Configuring dot1x
Table 5-34 Configuring dot1x
Configuring VoIP
Table 5-38 Configuring VoIP
voip : voip
qcelp : QCELP
cn : CN
g728 : G728
g729 : G729
codec2 : VoIP Media Profile (142)
Codec
pcmu : PCMU
gsm : GSM
g723 : G723
lpc : LPC
pcma : PCMA
g722 : G722
qcelp : QCELP
cn : CN
mpa : MPA
g728 : G728
g729 : G729
codec3 : VoIP Media Profile (142)
Codec
pcmu : PCMU
gsm : GSM
g723 : G723
lpc : LPC
g722 : G722
qcelp : QCELP
cn : CN
mpa : MPA
g728 : G728
g729 : G729
codec4 : VoIP Media Profile (142)
Codec
cn : CN
g722 : G722
g723 : G723
g728 : G728
g729 : G729
gsm : GSM
lpc : LPC
mpa : MPA
pcma : PCMA
pcmu : PCMU
qcelp : QCELP
on : on
voip : voip
gpon-onu- fax-mode : VoIP Media Profile (142)
voip fax-mode (passthru|t38)
profile Fax mode
passthru : Passthru
t38 : T.38
voip : voip
gpon-onu- jitter-buffer-max : Voice service
voip jitter-buffer-max
profile profile (58) Jitter buffer max
: The maximum depth of the jitter
buffer associated with this service in
milliseconds.
Config Voice service profile
voip : voip
Gpon-onu-
voip jitter-target jitter-target : Voice service profile
profile
(58) Jitter target
: The target value of the jitter buffer
in milliseconds,
Config VoIP Media Profile
voip : voip
gpon-onu- oob-dtmf : VoIP Media Profile (142)
voip oob-dtmf (on|off)
profile Out-of-band DTMF
off : Turn off silence suppression
voip : voip
packet-period1 : VoIP Media Profile
gpon-onu- voip packet-period1 packet-period2 (142) packet period
profile packet-period3 packet-period4
: This attribute specifies the packet
period selection interval in
milliseconds
packet-period2 : VoIP Media Profile
port : port
1 : port 1
gpon-onu- voip port (1|2) admin-state
profile (unlock|lock) 2 : port 2
admin-state : PPTP POTS UNI (53),
Administrative state
lock : all user functions of this
managed entity are blocked
unlock : managed entity is working
Config PPTP POTS UNI (53),
impedance
voip : voip
port : port
1 : port 1
2 : port 2
impedance : PPTP POTS UNI (53),
gpon-onu- voip port (1|2) impedance impedance
profile (600|900|complex1|complex2|complex3)
600 : 600 Ohms (omci value 0)
port : port
gpon-onu- 1 : port 1
voip port (1|2) rxgain WORD
profile
2 : port 2
voip : voip
port : port
1 : port 1
2 : port 2
5-89thernet5-89-code : VoIP voice
voip port (1|2) 5-89thernet5-89-code CTP (139): Signalling code: the
(loop-start|ground-start|loop- POTS-side signalling
gpon-onu-
reverse-battery|coin-first|multi- loop-start : Loop start
profile
party) 5-89thernet5-89-protocol-used
sip ground-start : Ground start
loop-reverse-battery : Loop reverse
battery
coin-first : Coin first
2 : port 2
port : port
1 : port 1
2 : port 2
gpon-onu- voip port (1|2) validation-scheme
profile (disabled|rfc-2069|rfc-2617) validation-scheme : Authentication
security method codes (148) :
Validation scheme
disabled : Disabled
rfc-2069 : MD5 digest authentication
in RFC 2069
rfc-2617 : Basic authentication in RFC
2617
Config SIP user data codes
voip : voip
port : port
1 : port 1
2 : port 2
voip port (1|2) voicemail-server-sip-
gpon-onu- voicemail-server-sip-uri : SIP user
uri A.B.C.D voicemail-subscription-
profile
expiration-time data codes (153), Voicemail server
sip uri
A.B.C.D : IP address
voicemail-subscription-expiration-
time : Voicemail subscription
expiration time
: Range 0 to 4294967295
voip : voip
A.B.C.D : IP address
: Range 0 to 4294967295(default
3600sec)
Config RTP profile data
voip : voip
voip : voip
5-91thernet5-91-protocol-used : VoIP
config data (138), specifies the VoIP
5-91thernet5-91 protocol to use
none : None protocol
voip : voip
tcp-udp-config-data : TCP/UDP
Config Data (136)
port-id : Port id
PORT_ID : The port number that
offers the TCP/UDP service
voip tcp-udp-config-data port-id protocol : Protocol, the protocol type
gpon-onu- PORT_ID protocol (tcp|udp) tos- as defined by IANA
profile diffserv-field TOS_DIFFSERV_FIELD ip-
tcp : TCP protocol
host <1-4>
udp : UDP protocol
Showing Profile
Table 5-41 Showing Profile
[en] show port gpon WORD onu index WORD Showing ACS information of GPON
acs-information ONU.
Table 5-44 Show GPON ONU Database & OMCI Logging history
(CCCCXXXXXXXX)
show counter of attached all onu
show : Show running system information
onu-attached-list : attached ONU entries
of GPON
en show onu-attached-list counter
port : Port
gpon : GPON port type
WORD : Port identifier
counter : count of attached-onu
Updating GPON-Module
Table 5-46 Updating GPON-Module
Clearing Information
Table 5-47 Clearing Information
65535>
clear port gpon WORD onu index
Clearing onu-omci-history log by Transaction
(all|WORD) onu-omci-history trans-id
ID of Index #
<1-65535>
This Chapter describes how to create/clear VLAN and add/clear port to VLAN. This chapter also describes
how to configure VLAN interface.
VLAN Configuration
VLAN Configuration
Default Configuration
The table below shows the default VLAN configuration for the Corecess S5 System:
Parameter Default
VLAN ID 1
IP address 0.0.0.0
Tag Untagged
After modifying the default VLAN configuration, modified configuration will be applied
immediately without rebooting system or using additional command. To maintain the modified
configuration after rebooting the system, save the configuration using write memory
command in Privileged mode.
You can configure VLAN on the Corecess S5 System using the following procedures:
2. Create VLAN
3. Assign ports to the defined VLAN (or clear ports from VLAN).
4. Save the VLAN configuration and apply the configuration to the system.
Creating VLANs
In the factory default configuration, VLAN support is enabled and all the ports are only in the
Corecess S5 System physical broadcast domain, which is given the name DEFAULT. You can
partition the Corecess S5 System into multiple virtual broadcast domains by adding one or
more additional VLANs and moving ports from the default VLAN to the new VLANs. Because
the default VLAN permanently exists in the Corecess S5 System, adding new VLANs results in
multiple VLANs existing in the Corecess S5 System.
VLAN is distinguished ID from other VLANs. VLAN ID and name can be specified by user.
The range of VLAN ID can be properly selected from 2 to 4094. Defining VLAN does not mean
that broadcast domain is created. When defined VLANs are added in ports, broadcast domain
is created with defined VLANs. Default VLANs in the system cannot be removed, and
ID/VLAN name cannot be changed.
Command Description
configure terminal 1. Enter Global configuration mode.
# configure terminal
(config)# vlan id 2 name test
(config)# end
# show vlan
To delete a VLAN, use the no vlan command in Global configuration mode. The following
example deletes the VLAN whose id is 2:
(config)# no vlan id 2
(config)#
You should add ports that belong to the same broadcast domain to a VLAN after defining a
VLAN. When ports are assigned to a VLAN, a broadcast domain with assigned ports is created.
If you add ports belonging to the default VLAN to other VLAN, the ports are deleted from the
default VLAN and are added to other VLAN.
To add ports to a VLAN, use the following commands.
Commands Description
configure terminal 1. Enter Global configuration mode.
33. Assign the specified ports to the VLAN.
Vlan {id <vlan-id> |
<vlan-id> VLAN ID (2 ~ 4094)
name <vlan-name>}
<vlan-name> VLAN name
port gigabitethernet
<slot>/<port> slot number / port number to be added to
<slot>/<port>
the VLAN
end 3. Return to Privileged mode.
The following example shows how to add the Gigabit Ethernet port 5/4 to the VLAN that the
ID is 2:
# configure terminal
(config)# vlan id 2 port gigabitethernet 5/4
(config)# end
# show vlan id 2
VLAN Name Status Slot/Ports
---- ---------------- -------- ------------------------------------
2 test active 5/4
Commands Description
configure terminal 1. Enter Global configuration mode.
This example shows how to specify the IP address of the VLAN whose id is ‘1’:
You can specify another IP address to a VLAN. This is called ‘secondary’ IP address. Secondary
IP address is useful that the number of hosts is more than the number of IP addresses.
To specify the secondary IP address to the VLAN, use the following command in Global
configuration mode:
Command Description
configure terminal 1. Enter Global configuration mode.
This example shows how to specify the secondary IP address of the VLAN whose id is ‘1’:
# configure terminal
(config)# interface vlan id 1
(config-if)# ip address 172.25.1.100/16 secondary
(config-if)# end
# show interface vlan id 1
Interface vlan1
index 28 kernel index 4 metric 1 mtu 1500 <UP,BROADCAST,RUNNING,MULTICAST>
Hwaddr: 00:01:02:00:00:db
inet 172.27.2.100/16 broadcast 172.27.255.255
inet 172.25.1.100/16 broadcast 172.25.255.255 secondary
input packets 14926, bytes 899535, dropped 0, multicast packets 6491
input errors 0, length 0, overrun 0, CRC 0, frame 0, fifo 0, missed 0
output packets 474, bytes 414, dropped 0
output errors 0, aborted 0, carrier 0, fifo 0, heartbeat 0, window 0
collisions 0
If 802.1Q trunk is applied, the devices can share their VLANs. Because a switch generally does
not know VALN information of other switch, the switch cannot share VALN. Thus, nodes that
connected to several devices cannot be configured to be included in the same VLAN. In this
occasion, if traffic that has VLAN information is transmitted by 802.1Q trunk, because the
switch that receives traffic recognizes VLAN information and can forward traffic to the
corresponding VLAN, VLANs can be shared between switches.
802.1Q truck is generally used for VPN (Virtual Private Network).
To configure trunk ports for 802.1Q tunneling, use the following commands.
Command Description
configure terminal 1. Enter Global configuration mode.
Dot1q port gigabitethernet 41. Specify 802.1Q trunk port.
<slot>/<port> tag <tag-id> <slot>/<port> Slot/Port number of trunk port
[<tag-id> … ] <tag-id> VLAN ID
end 3. Return to the Privileged mode.
Show dot1q port 4. Verify the 802.1Q trunk port configuration.
If 802.1Q trunk port is configured on the Corecess S5 System as above, traffic is transmitted
through the tunnel between 802.1Q trunk port of the connected neighbor device and the
Corecess S5 System. Traffic is also received from 802.1Q trunk port that is defined on the
Corecess S5 System. The trunk port that received traffic does not remove 802.1Q tag of the
traffic header but forward all received 802.1Q traffic to the VLAN that has the trunk port
instead.
The VLAN that has the trunk port transmits the subscriber traffic to other neighbor device that
is included in the VLAN of the trunk port. When the traffic reaches to the final destination,
802.1Q tag is removed, traffic is removed from the tunnel.
The following example shows how to specify 802.1Q trunk port and verify the result.
# configure terminal
(config)# vlan id 2 port gigabitethernet 17/1,17/2
(config)# dot1q port gigabitethernet 17/1 tag 1-2
(config)# end
# show dot1q
Port allowed 802.1q VLAN TAGs
-------- -----------------------------------------------------------------
17/1 1-2
# show dot1q port gigabitethernet 17/1
Port PVID Acceptable frame types Ingress filter
---------- ---- ---------------------- --------------
17/1 2 all off
Port allowed 802.1q Vlans
-------- -----------------------------------------------------------------
17/1 1-2
#
Configuring Q in Q
The ‘802.1Q-in-802.1Q’ technology which is commonly called Q-in-Q is able to raise
extensibility as the number of VLAN’s managed as a whole is reduced by dividing the 802.1Q
grouping VLAN into many 802.1Q’s once again.
Q-in-Q Features
The Q-in-Q function provided in this equipment is operated by having the following features.
Q-in-Q Setup
The Q-in-Q setup assigns subscriber port and assigns the PVID of corresponding subscriber
port as a tag at the ISP Uplink port.
Command Description
configure terminal Enter Privileged mode.
The following is an example of setup to provide the Q-in-Q service by adding the VLAN Tag
1000 times for VLAN Tag attached packets that are coming up from the subscriber port.
# configure terminal
(config)# vlan id 1000 port gigabitethernet 3/3
(config)# dot1q-tunnel port gigabitethernet 3/3
(config)# dot1q port gigabitethernet 1/1 tag 1000
(config)# dot1q port gigabitethernet 1/2 tag 1000
(config)#
Command Description
configure terminal Enter Global configuration mode.
The above is an example of activating the BPDU Transparent Switching function for subscribers
of gigabitethernet 3/1 port among the example above.
(config)#
(config)# vlan id 1000 pass-thru bpdu
(config)# port gigabitethernet 3/1 pass-thru bpdu
(config)# port gigabitethernet 1/1-2 pass-thru bpdu
(config)# vlan id 1000 pass-thru q-in-q
(config)# port gigabitethernet 3/1 pass-thru q-in-q
(config)# port gigabitethernet 1/1-2 pass-thru q-in-q
(config)#
Command Description
configure terminal Enter Global configuration mode.
The following example shows how to set Priority Copy on the gigabitethernet 3/2 port.
(config)#
(config)# port gigabitethernet 3/2 priority-copy
(config)#
The following example shows how to enter Interface configuration mode to configure VLAN
interface that ID is 1.
You have entered interface configuration mode when the prompt changes to (config-if)#.
You can configure the followings of the VLAN interface on Interface configuration mode:
Note: To specify the IP address of the VLAN interface, refer to Assigning the IP address
of a VLAN section in this chapter.
Parameter Description
OSPF supports three methods of authentication for each interface—none, simple
password, and MD5.
None : Send/Receive OSPF routing packet without any authentication mode.
Simple Password : The simple password method of authentication requires you
to configure an alphanumeric password on an interface. The simple password
setting takes effect immediately. All OSPF packets transmitted on the interface
Authentication contain this password. Any OSPF packet received on the interface is checked
Mode for this password. If the password is not present, then the packet is dropped.
MD5 : The MD5 method of authentication requires you to configure a key ID
and an MD5 Key. The key ID is a number from 1 – 255 and identifies the MD5
key that is being used. The MD5 key can be up to sixteen alphanumeric
characters long.
Only one method of authentication can be active on an interface at a time. The
default authentication value is none, meaning no authentication is performed.
In Simple Password authentication method, the key can be up to eight characters
Authentication long. In MD5(Message Digest) authentication method, the key ID is a number from
Key 1 – 255 and identifies the MD5 key that is being used. The MD5 key can be up to
sixteen alphanumeric characters long.
The overhead required to send a packet across an interface. You can modify the cost
to differentiate between 100 Mbps and 1000 Mbps (1 Gbps) links. The default cost is
Cost calculated by dividing 100 million by the bandwidth. For 10 Mbps links, the cost is
10. The cost for both 100 Mbps and 1000 Mbps links is 1, because the speed of 1000
Mbps was not in use at the time the OSPF cost formula was devised.
The number of seconds that a neighbor router waits for a hello packet from the
Dead-interval current router before declaring the router down. The value can be from 1 – 65535
seconds. The default is 40 seconds.
The length of time between the transmissions of hello packets. The value can be
Hello-interval
from 1 – 65535 seconds. The default is 10 seconds.
The time between retransmissions of link-state advertisements (LSAs) to adjacent
Retransmit-
routers for this interface. The value can be from 0 – 3600 seconds. The default is 5
interval
seconds.
The time it takes to transmit Link State Update packets on this interface. The value
Transmit-delay
can be from 0 – 3600 seconds. The default is 1 second.
Network The OSPF network type. The default network type is broadcast.
The priority allows you to modify the priority of an OSPF router. The priority is
used when selecting the designated router (DR) and backup designated routers
Priority
(BDRs). The value can be from 0 – 255. The default is 1. If you set the priority to 0,
the Corecess S5 System does not participate in DR and BDR election.
In simple Password authentication method, a particular key is specified for each area. Routers
in the same area should use the same key. This method has a disadvantage that the key can be
disclosed because the key is not encrypted.
To set simple authentication key and password authentication method, use the following
commands.
Command Description
configure terminal 1. Enter Global configuration mode.
Interface vlan id 42. Enter Interface configuration mode.
<vlan-id> <vlan-id> VLAN interface ID (1 ~ 4094)
ip ospf authentication- 43. Specify password for authentication.
key <key> <key> password (8 character, 16byte)
exit 4. Return Global configuration mode.
Router ospf 5. Enter OSPF configuration mode.
Area <area-id>
6. Set simple password authentication method in the specified area.
authentication
The following example shows how to set simple password authentication method.
To remove the key of the specified simple password authentication method, use no ip ospf
authentication-key command.
MD5 (Message Digest) authentication assign a key and key identifier to each router. The router
makes authentication information(Message digest) using OSPF packets, key, and key identifier.
This authentication information will be appended to OSPF packets and sent.
In general, one key is used per interface to generate authentication information when sending
packets and to authenticate incoming packets. The same key identifier on the neighbor router
must have the same key value.
The following example shows that the new MD5 password is added over the existing MD5
password.
The system assumes its neighbors do not have the new key yet, so it begins a rollover process. It
sends multiple copies of the same packet, each authenticated by different keys. In this example,
the system sends out two copies of the same packet—the first one authenticated by key 100 and
the second one authenticated by key 101.
Then, only key 101 is used for authentication on the interface eth1. We recommend that you not
keep more than one key per interface. Every time you add a new key, you should remove the
old key to prevent the local system from continuing to communicate with a hostile system that
knows the old key. Removing the old key also reduces overhead during rollover.
The following example sets a new key 100 with the password mypasswd on interface vlan1:
Each interface can have only one cost in the Corecess S5 System. The cost of OSPF interface is
calculated by the following formula depending on interface bandwidth.
If interface cost using above formula is not preferable to be used to user network, use ip ospf
cost command to specify cost to each interface in Interface configuration mode.
Command Description
The following example sets the cost value of a VLAN interface to 10:
Specifying Dead-Interval
Dead-interval indicates the number of seconds that a neighbor router waits for a hello packet
from the current router before declaring the router down. The value can be from 1 – 65535
seconds. The default is 40 seconds.
Command Description
ip ospf dead-interval <seconds> Unsigned integer that specifies the interval in seconds;
<seconds> the value must be the same for all nodes on the network (1 ~ 65535)
Specifying Hello-Interval
Hello-interval represents the length of time between the transmissions of hello packets. The
value can be from 1 – 65535 seconds. The default is 10 seconds. To specify the hello-interval, use
the following commands in Interface configuration mode:
Command Description
The following example sets the interval between hello packets to 15 seconds:
Command Description
The following example sets the retransmit-interval value of the interface vlan1 to 8 seconds:
Transmit delay is the time it takes to transmit Link State Update packets on the interface. The
value can be from 1 – 65535 seconds. The default is 1 second. To specify the transmit delay, use
the following commands in Interface configuration mode:
Command Description
ip ospf ospf transmit- <seconds>: Time in seconds that it takes to transmit a link state
delay <seconds> update (1 ~ 65535).
The following example sets the retransmit-delay value of the interface vlan 1 to 3 seconds:
Specifying Priority
Priority allows you to modify the priority of an OSPF router. The priority is used when
selecting the designated router (DR) and backup designated routers (BDRs). The value can be
from 0 – 255. The default is 1. If you set the priority to 0, the system does not participate in DR
and BDR election.
To set the router priority, use the following commands in Interface configuration mode:
Command Description
The following example sets the router priority value to 4 of the interface vlan1:
Parameter Description
Hello Padding Enables or disables hello padding for IS-IS hello packets.
Hello Multiplier Specifies the hello multiplier for calculating the hold time.
LSP interval Configures the delay between successive IS-IS link state packet transmissions
Configures the number of seconds between retransmission of IS-IS LSPs for
Retransmit Interval
point-to-point links.
Mesh Group Creates a mesh group and designate that an interface is part of the group.
Metric Configure a cost for a specified interface.
Password Configures a password for a specified interface.
Priority Configures the priority of designated router (DR).
Note: Most interface configuration commands can be configured independently from other
attached routers. But the isis password command should configure the same password
on all routers on a network.
You specify the IS-IS level on a per-interface basis, and the Corecess S5 System becomes
adjacent with other routers on the same level on that link only. The Corecess S5 System
supports the following IS-IS levels:
Level-1
Establish a Level 1 adjacency if there is at least one area address in common between this
system and its neighboring systems. If Level 1 is set, this interface cannot support Level 2
adjacencies.
Level-1-2
Establish a Level 1 and Level 2 adjacency if a neighboring system is also configured as a Level
-1-2 and there is at least one area address in common. If there is no area address in common, a
Level 2 adjacency is established.
Level-2-only
Establish a Level 2 adjacency if the neighboring system is configured as a Level 2-only router.
To configure the type of IS-IS adjacency for an interface, enter the isis circuit-type
command in Interface configuration mode:
Command Description
The following example shows how to configure the VLAN interface to support a Level-2
adjacency:
Note: Normally, this command does not need to be configured. Only on routers that are
between areas (Level 1-2 routers) should you configure some interfaces to be Level 2-only
to prevent wasting bandwidth by sending out unused Level 1 hellos. Note that on point -to-
point interfaces, the Level 1 and Level 2 hellos are in the same packet.
All IS-IS routes have a cost, which is a routing metric that is used in the IS-IS link-state
calculation. The cost is an arbitrary, dimensionless integer that can be from 1 through 63. The
default metric value is 10.
To modify the default value, enter the isis metric command in Interface configuration
mode:
Command Description
<metric-value> The default metric is used as a value for the IS-IS
isis metric
metric. Valid values are 0 – 63.
<metric-value>
level-1 Configures the metric only for level-1 routing.
[level-1 | level-2]
level-2 Configures the metric only for level-2 routing.
The following example shows how to configure the default metric for the VLAN interface:
Note: If no level is specified, the isis metric command configures the metric for level-1
routing only.
On broadcast networks, designated routers send complete sequence number PDU (CSNP)
packets to maintain database synchronization. The CSNP interval timer is the number of
seconds between transmissions of CNSP packets from this interface.
The CSNP interval is configured independently for Level 1 and Level 2. This feature does not
apply to point-to-point interfaces. To modify the CSNP interval, enter the csnp-interval
command in Interface configuration mode.
Command Description
<seconds> The interval of time between transmissions of CSNPs on
broadcast networks. This interval only applies to the designated
isis csnp-interval router. This can be a number between 0 and 65535 seconds.
<seconds> [level-1| level-1 Configures the amount of time between transmissions of
level-2] CSNPs for Level 1 independently.
level-2 Configures the interval of time between transmission of
CSNPs for Level 2 independently.
The following example shows how to configure the transmission interval for CSNP packets:
To modify how often the system sends hello packets out of an interface, enter the isis
hello-interval command in Interface configuration mode.
Command Description
<seconds>: Number of seconds between transmissions of hello
packets. Valid values are between 1 and 65535 seconds.
isis hello-interval
minimal:. Causes the system to compute the hello interval based on
{<seconds>|minimal}
the hello multiplier so that the resulting hold time is 1 second.
[level-1|level-2]
level-1: Configures the hello interval for Level 1 independently
level-2: Configures the hello interval for Level 2 independently
The following example shows how to configure the VLAN interface to advertise hello packets
every 5 seconds:
If the minimal keyword is specified, the hold time is 1 second and the system computes the
hello interval based on the hello multiplier as follow:
The hello multiplier determines the total holding time transmitted in the IS-IS hello packet.
Holding time is the time a neighbor waits for another hello packet before declaring the neighbor
is down.
The hello interval times multiplied by the hello multiplier equals the hold time. If the hello
interval is 10 seconds and the hello multiplier is 3, the hold time is 30 seconds.
To modify the hello multiplier, enter the isis hello-multiplier command in Interface
configuration mode.
Command Description
<multiplier>: The multiplier used to determine how long to
hold an IS-IS hello packet before declaring an adjacency down.
isis hello-multiplier Valid values are 3 – 1000.
<multiplier> level-1: Configures the hello multiplier independently for Level
[level-1|level-2] 1 adjacencies.
level-2: Configures the hello multiplier independently for Level
2 adjacencies.
The following example configures the hello interval and hello multiplier to 6 and 10. As the
result, an adjacency will go down only when many (10) hellos are missed and the total time to
detect link failure is 60 seconds.
Padding adds extra characters to the hello packets so that all packets sent out by Is-IS have the
maximum sized data payload.
To enable hello padding for IS-IS hello packets, enter the isis hello padding command in
Interface configuration mode as follows:
To configure the time delay between successive IS-IS link state packet transmissions, enter the
isis lsp-interval command in Interface configuration mode.
Command Description
isis lsp-interval <milliseconds>: Time delay between successive link state packets.
<milliseconds> Valid values are 1 ~ 4294967295.
The default LSP interval is 33 milliseconds. The following example configures the LSP interval
to 100 milliseconds (10 packets per second) on the VLAN interface:
To configure the amount of time between retransmission of each IS-IS LSP on a point-to-point
link, enter the isis retransmit-interval command in Interface configuration mode.
Command Description
The following example shows how to configure the LSP retransmit interval to 60 seconds:
(config)# interface vlan id 1
(config-if)# isis retransmit-interval 60
(config-if)#
A mesh group is a set of routers that are fully connected; that is, they have a fully meshed
topology. When LSP packets are being flooded throughout an area, each router within a mesh
group receives only a single copy of an LSP packet instead of receiving one copy from each
neighbor, thus minimizing the overhead associated with the flooding of LSP packets.
To create a mesh group and designate that an interface is part of the group, enter the isis
mesh-group command in Interface configuration mode.
Command Description
In the following example show how to configure the VLAN interfaces to be a member of the
mesh group 3:
You can prevent unauthorized routers from forming adjacencies with the Corecess S5 System,
and thus protects the network from intruders.
To configure the authentication password for an interface, enter the isis password
command in Interface configuration mode.
Command Description
<string>: Authentication password you assign for an interface.
isis password level-1: Configures the authentication password for Level 1
<string> [level-1 | independently.
level-2] level-2: Configures the authentication password for Level 2
independently.
The following example configures a password for the VLAN interface:
(config)# interface vlan id 1
(config-if)# isis password corecess
The priority is used to determine which router on a LAN will be the designated router (DR) or
Designated Intermediate System (DIS). The priorities are advertised in the hellos. The router
with the highest priority will become the DIS. In the case of equal priorities, the highest MAC
address breaks the tie.
To configure the priority of DR, enter the isis priority command in Interface configuration
mode.
Command Description
isis priority <priority> The priority of a router and is a number from 0 to 127.
<priority> level-1 Sets the priority for Level 1 independently.
[level-1 | level-2] level-2 Sets the priority for Level 2 independently.
The following example shows how to set the priority level to 80:
Parameters Description
RIP supports two methods of authentication for each interface— simple
password and MD5. Only one method of authentication can be active on an
interface at a time.
• The simple password method of authentication requires you to configure an
alphanumeric password on an interface. The simple password setting takes
effect immediately. All OSPF packets transmitted on the interface contain this
authentication mode password. Any OSPF packet received on the interface is checked for this
password. If the password is not present, then the packet is dropped. The
password can be up to eight characters long.
• The MD5 method of authentication requires you to configure a key ID and an
MD5 Key. The key ID is a number from 1 – 255 and identifies the MD5 key
that is being used. The MD5 key can be up to sixteen alphanumeric
characters long.
In Simple Password authentication method, the key can be up to eight
characters long. In MD5(Message Digest) authentication method, the key ID is a
Authentication Key
number from 1 – 255 and identifies the MD5 key that is being used. The MD5
key can be up to sixteen alphanumeric characters long.
RIP version RIP version can be specified to each interface.
Split Horizon function is that the same route information cannot be transmitted
Split Horizon
to the interface if route information is received form a particular interface.
This section describes how to configure RIP parameter in VLAN interface.
RIP version 2 provides authentication function to check receiving routing information is secure.
RIP does not add a new field to packets for authentication, but uses the first entry of message as
authentication key. RIP specifies key chain as the key to be used for authentication. Key chain is
a group of keys. If key chain is specified for each interface, the key of key chain is used when
authentication proceeds.
There are two authentication mode-Simple password and MD5. By default, simple password
mode is used. In Simple password mode, the key is transmitted without any encryption. Thus,
if authentication is used for security, the mode is inappropriate. In MD5 authentication mode,
the key is encrypted to “message digest” using MD5 algorithm, then the message digest is
transmitted instead of the key.
Command Description
configure terminal 1. Enter Global configuration mode.
Interface vlan id 44. Enter Interface configuration mode.
<vlan-id> <vlan-id> VLAN interface ID (1 ~ 4094)
ip rip authentication
45. Specify the type of key for authentication
key-chain
<name-of-chain> <name-of-chain> Name of key group (key chain).
Ip rip authentication
4. Specify MD5 authentication mode.
mode md5
To authenticate RIP packets with MD5 authentication mode, specify the type of key to use for
authentication using ip rip authentication key-chain command. Then, specify which
authentication mode will used between simple password and MD5. By default, simple
password authentication mode is specified.
# configure terminal
(config)# key chain corecess
(config-keychain)# key 1
(config-keychain-key)# key-string 234
(config-keychain-key)# exit
(config-keychain)# exit
(config)# interface vlan id 1
(config-if)# ip rip authentication key-chain corecess
(config-if)# ip rip authentication mode md5
If you cancel the specified authentication mode and back to the default, use no ip rip
authentication mode command. And, if you cancel the key chain that is used for
authentication, use no ip rip authentication key-chain command.
Command Description
configure terminal 1. Enter Global configuration mode.
Interface vlan id 46. Enter Interface configuration mode.
<vlan-id> <vlan-id> VLAN interface ID (1 ~ 4094)
ip rip authentication 47. Specify the type of key
string <auth-string> <auth-string> Authentication string (less than 16 character)
ip rip authentication
4. Specify simple password authentication mode.
mode text
The following example shows how to set simple password authentication method.
To remove the key of the specified simple password authentication method, use no ip rip
authentication-key command.
To specify a Routing Information Protocol (RIP) version on an interface basis, use the following
commands in Interface configuration mode:
Command Description
configure terminal 1. Enter Global configuration mode.
Interface vlan id 48. Enter Interface configuration mode.
<vlan-id> <vlan-id> VLAN interface ID (1 ~ 4094)
49. Specify RIP version to receive.
ip rip receive <version> RIP version (1, 2)
version <version> -1 :Accepts only RIP Version 1 packets on the interface.
-2 :Accept only RIP Version 2 packets on the interface.
- 1 2 : Accepts both RIP Version 1 and 2 packets on the interface.
50. Specify RIP version to send.
Ip rip send version <version> RIP version (1, 2)
<version> -1 :Sends only RIP Version 1 packets out the interface.
-2 :Sends only RIP Version 2 packets out the interface.
- 1 2 : Sends both RIP Version 1 and 2 packets out the interface.
The following example configures the interface to receive both RIP Version 1 and Version 2
packets:
# configure terminal
(config)# interface vlan id 1
(config-if)# ip rip receive version 1 2
The following example configures the interface to send both RIP Version 1 and Version 2
packets out the interface:
# configure terminal
(config)# interface vlan id 2
(config-if)# ip rip send version 2
Enabling Split-Horizon
RIP can use the “split-horizon” to prevent routing loops. The split horizon is the function that
the router does not advertise a route on the same interface as the one on which the router
learned the route.
Command Description
configure terminal 1. Enter Global configuration mode.
# configure terminal
(config)# interface vlan id 1
(config)# ip split-horizon
(config)#
To disable the split horizon mechanism, use the no ip split-horizon command in Interface
configuration mode.
Command Description
configure terminal 1. Enter Global configuration mode.
The multicast packet forward on the interface is enabled by default. To disable the multicast
packet forward, use the no multicast command.
The following is an example of disabling the multicast packet forward of the interface vlan1:
Command Description
configure terminal 1. Enter Global configuration mode.
This example shows how to shut down the interface vlan1 and re-enable the interface:
Hwaddr: 00:01:02:00:00:db
inet 172.27.2.100/16 broadcast 172.27.255.255
input packets 18181, bytes 1094835, dropped 0, multicast packets 6759
input errors 0, length 0, overrun 0, CRC 0, frame 0, fifo 0, missed 0
output packets 1069, bytes 966, dropped 0
output errors 0, aborted 0, carrier 0, fifo 0, heartbeat 0, window 0
collisions 0
Configuring IP Parameters
Table below lists the IP global parameters for the VLAN interface on the Corecess S5 System:
Parameter Description
MTU The maximum length an Ethernet packet can be without being
(Maximum Transmission Unit) fragmented
A standard IP mechanism that routers use to learn the Media Access
ARP Control (MAC) address of a device on the network. The router sends
(Address Resolution Protocol) the IP address of a device in the ARP request and receives the
device’s MAC address in an ARP reply.
To configure the parameters above for the VLAN interface, use the following commands in
interface configuration mode:
Command Description
configure terminal 1. Enter Global configuration mode.
Interface vlan id 54. Enter Interface configuration mode.
<vlan-id> <vlan-id> ID of the VLAN to configure. (1 ~ 4094)
arp 3. Enables the ARP on the VLAN interface.
Arp <ip-address>
4. Adds a static ARP (Address Resolution Protocol) entry.
<hw-address>
55. Changes the size of the MTU (Maximum Transmission Unit)
Mtu <mtu-size> on the VLAN interface.
<mtu-size> Size of the MTU (64 ~ 9000bytes, default : 1514)
메모 [zwyi1]: 변경
Private VLAN
The Private VLAN provides L2 isolation between subscriber’s ports. Ports belonging to a
private VLAN are associated with a common set of supporting VLANs that are used to create
the private VLAN structure. Here are two types of private VLAN ports: promiscuous and
isolated. A promiscuous port communicates with all other private VLAN ports and is the port
you use to communicate with routers. An isolated port has complete L2 separation from other
ports within the same private VLAN with the exception of the promiscuous port.
A typical application is at a hotel where each room has a port that can access the Internet. In this
situation it is undesirable to allow communication between rooms. Another application is to
simplify IP address assignment. Ports can be isolated from each other while belonging to the
same subnet.
Command Description
configure terminal 1. Enter Global configuration mode.
Vlan id 1 private-vlan
56. Setting default vlan id 1
promisc-port port type
<slot>/<port> Slot/Port number of promisc-port.
<slot>/<port>
End 3. Return to the Privileged mode.
Show vlan 4. Verify the vlan promiscuous port configuration.
No vlan id 1 private-vlan 5. Disable private vlan.
# configure terminal
(config)# vlan id 1 private-vlan promisc-port gigabitethernet 18/1
(config)# end
(config)#
This chapter describes how to configure SNMP and RMON on the Corecess S5 System.
Configuring SNMP
Configuring SNMP
SNMP(Simple Network Management Protocol)
Overview
The Simple Network Management Protocol (SNMP) is an application layer protocol that
facilitates the exchange of management information between network devices. It is part of the
Transmission Control Protocol/Internet Protocol (TCP/IP) protocol suite. SNMP enables
network administrators to manage network performance, find and solve network problems,
and plan for network growth.
Managed Device
SNMP Manager
SNMP
Manager
Managed Device
A managed device is a network node that contains an SNMP agent and that resides on a
managed network. Managed devices collect and store management information and make this
information available to NMSs using SNMP. Managed devices, sometimes called network
elements, can be routers and access servers, switches and bridges, hubs, computer hosts, or
printers.
Get a MIB variable: The SNMP agent initiates this function in response to a request from
the NMS. The agent retrieves the value of the requested MIB variable and responds to the
NMS with that value.
Set a MIB variable: The SNMP agent initiates this function in response to a message from
the NMS. The SNMP agent changes the value of the MIB variable to the value requested
by the NMS.
The SNMP agent also sends unsolicited trap messages to notify an NMS that a significant event
has occurred on the agent. Examples of traps conditions include, but are not limited to, when a
port or module goes up or down, when spanning-tree topology changes occur, and when
authentication failures occur.
The MIB is the information base, the SNMP agent must keep available for the managers. This
information base contains objects whose values provide information on the status of the
checked system or objects whose values can be modified by a manager to control the system.
Each object is identified by an Object ID (OID). There are two kinds of MIBs, standard MIB
and enterprise-specific MIB.
SNMP Manager
SNMP Manager is an integrated management module which collects information from SNMP
agent and sometimes sends warning messages depending on the each SNMP agent relations. In
other words, the actual data is collected from SNMP agent and this data will be processed by
management module and saved. To request information or configuration changes, respond to
requests, and send unsolicited alerts, the SNMP manger and SNMP agent use the four messages
(Get, GetNext, Set, and trap). For more information on these messages, refer to the following
section.
SNMP Messages
The SNMP manger and SNMP agent use the following SNMP messages to request information
or configuration changes, respond to requests, and send unsolicited alerts.
Get-Request Message
Get-Request Message is the basic SNMP request message. Sent by an SNMP manager, it
requests information about a single MIB entry on an SNMP agent. For example, the amount of
free drive space.
GetNext-Request Message
GetNext-Request Message is an extended type of request message that can be used to browse
the entire tree of management objects. When processing a Get-next request for a particular
object, the agent returns the identity and value of the object which logically follows the object
from the request. The Get-next request is useful for dynamic tables, such as an internal IP route
table.
Set-Request Message
If write access is permitted, Set-Request message can be used to send and assign an updated
MIB value to the agent.
Trap Message
An unsolicited message sent by an SNMP agent to an SNMP manager when the agent detects
that a certain type of event has occurred locally on the managed device. For example, a trap
message might be sent on a system restart event.
SNMP Community
SNMP community authenticates access to MIB objects and function as embedded passwords. In
order for the NMS to access the system, the community definitions on the NMS must match at
least one of the two community definitions on the system.
A community can have one of the following attributes:
Trap
Trap is a defined status of event or system. For example, event generated when port
configuration is changed or a host having not-allowed IP address accesses can be defined as a
trap. You can configure the level of trap according to the kind of events.
If a trap occurs on the system, the SNMP agent send SNMP trap message to the registered trap
host.
Configuring SNMP
The default SNMP configuration of the Corecess S5 System is as follows:
RMON Enabled
In the system group of MIB-II (Public MIB) supported by the Corecess S5 System has System
Contact variable and System Location variable displaying the system contact information and
system location information.
The values of these variables can be browsed or modified via ViewlinX, NMS of the Corecess or
NMS of other companies.
Command Description
configure terminal 1. Enter Global configuration mode.
The following is an example of setting the system contact information and system location
information:
# configure terminal
(config)# snmp-server contact Dial System Administrator at phone #2734
(config)# snmp-server location 1st_floor lab
(config)# end
# show snmp-server
RMON: Enabled
Extended RMON: Extended RMON module is not present
Configuring Community
You use the SNMP community to define the relationship between the SNMP manager and the
agent. The community acts like a password to permit access to the agent on the system. One
thing to be aware of is that in case of adding new community using the Corecess S5 System CLI
command, this community must be added in NMS in order to connect to the system using this
community. To define SNMP community, use the following commands in Privileged mode:
Command Description
configure terminal 1. Enter Global configuration mode.
59. Define the SNMP community for each access type.
<string> The SNMP community name for this system
Snmp-server community
<string> <auth> <auth> Access authentication of the community
- ro This authority can only read a value.
- rw This authority can read and write a value.
End 3. Return to Privileged mode.
Show snmp-server 4. Verify new community string.
# configure terminal
(config)# snmp-server community corecess rw
(config)# end
# show snmp-server
RMON: Enabled
Extended RMON: Extended RMON module is not present
Community-Access Community-String
---------------- ----------------
read-only public
read-write private
read-write corecess
.
.
#
Procedure Description
view
test
view
test2
You can create view name and MIB OID include or excluded with the following commands.
excluded : exclude
WORD : MIB object ID(ex: .1.3.6)
notify-name.
Configuring Trap
Traps are system alerts that the Corecess S5 System generates when certain events occur.
When a trap is enabled, if an error occurs in the device where corresponding trap is enabled or
if problem occurs in the part defined by the trap, such error status (trap message) are
transmitted to the trap receiving host and NMS, the SNMP agent. By default, all trap types are
disabled. To send traps to the trap hosts, the trap types should be enabled.
Command Description
configure terminal 1. Enter Global configuration mode.
2.. Enable the specified trap type
<trap-type> Trap type to be enabled
Snmp-server enable
(all, auth, bgp, bridge, chassis, cpuload, dhcp,
traps <trap>
entity, ip_permit, module, port, repeater, sysauth,
sysconfig). If you choose all, all traps become enabled.
End 3. Return to Privileged mode.
Show snmp-server 4. Check the state of the trap.
# configure terminal
(config)# snmp-server enable traps port
(config)# snmp-server enable traps auth
(config)# end
# show snmp-server
RMON: Enabled
Extended RMON: Extended RMON module is not present
.
.
Trap-Rec-Address Trap-Rec-Community
------------------------- ------------------
Traps Enabled
------------------------- ------------------
chassis disabled
module disabled
port enabled
bridge disabled
repeater disabled
ip_permit disabled
sysconfig disabled
entity disabled
cpuload disabled
auth enabled
sysauth disabled
bgp disabled
dhcp disabled
atm disabled
adslAtuc disabled
adslAtur disabled
mac-flood disabled
#
To disable the trap type, use the no snmp-server enable traps command as follows:
To disable the trap of specified module, use the following commands in Privileged mode:
Command Description
configure terminal 1. Enter Global configuration mode.
No snmp-server enable
traps module <Module or 2. Disable the trap of specified module.
slot identifier>
End 3. Return to Privileged mode.
Show running-config 4. Check the state of the trap.
The following example shows how to disable the trap of specified module:
# configure terminal
(config)# no snmp-server enable traps module 1
Trap host is the host to receive traps from an SNMP agent. Trap is message sent by an SNMP
agent to an NMS, a console, or a terminal to indicate the occurrence of a significant event, such
as a specifically defined condition or a threshold that was reached. By default, no trap host is
configured. To receive the trap generated on your managed device using NMS, you must add
the NMS as a trap host. You can specify up to twenty trap hosts on the Corecess S5 System.
To add or modify trap hosts, use the following commands in Privileged mode:
Command Description
configure terminal 1. Enter Global configuration mode.
Snmp-server host <ip-address> 60. Configure trap hosts.
<community> port {<udp-port> <host-addr> The IP address of an SNMP host that been
| configured to receive traps.
default}version(v1|v2|infor <community> The community name to use when
When a trap host is added, the community of the host should be specified. The type of trap
message, which the host receives, is decided by the specified community.
# configure terminal
localhost(config)# snmp-server host 172.18.80.64 public port default version
inform
localhost(config)# end
localhost# show snmp-server traphost
Trap Source IP
-------------------------
Default : 172.18.150.2
localhost#
You can set SNMP v3 trap-host and inform-trap-host as authentication mode with the following
command.
“host engineid”
You can set SNMP v3 trap-host and inform-trap-host as privacy mode. (Only for SCM-B208G)
For disabling the SNMP trap host setting, Use the following command.
The following examples show how to add a trap host according to SNMP trap version and
configured information.
RMON: Enabled
Extended RMON: Extended RMON module is not present
sysContact support@corecess.com
sysLocation Corecess Inc.
Traps Enabled
------------------------- ------------------
com2sec,com2sec6,group,view,access,user configs
host : udp:172.18.70.105:162
version : v1
type : trap
community : public
Trap Source IP
-------------------------
Default : 172.18.150.2
The Corecess S5 System can restrict hosts that attempt to access to the Corecess S5 System with
SNMP using access list. Only hosts that are satisfied with the access list condition can be access
the system with SNMP.
To restrict host by using access lists, use the following commands in Global configuration mode:
Command Description
snmp-server group
Apply the defined access list.
access
<list-number> number of access list (1 ~ 99, 100 ~ 199)
<list-number>
The following example shows how to define the access list to restrict host access and apply the
access list.
# show snmp-server
RMON: Disabled
Extended RMON: Extended RMON module is not present
sysContact support@corecess.com
sysLocation Unknown
Community-Access Community-String
---------------- ----------------
read-only public
read-write private
Trap-Rec-Address Trap-Rec-Community
------------------------- ------------------
udp:172.27.2.36:162
Traps Enabled
------------------------- ------------------
chassis disabled
module disabled
port disabled
bridge disabled
repeater disabled
ip_permit disabled
sysconfig disabled
entity disabled
cpuload disabled
auth disabled
sysauth disabled
bgp disabled
dhcp disabled
atm disabled
adslAtuc disabled
adslAtur disabled
mac-flood disabled
#
The table below describes the fields shown by the show snmp-server command:
Field Description
RMON Status of whether RMON is enabled or disabled.
Extended RMON Status of whether extended RMON is enabled or disabled.
sysContact SNMP system operator information
sysLocation SNMP system location information string
SNMP access authority
Community-Access - read-only
community - read-write
SNMP community strings associated with each SNMP
Community-String
community
IP address of trap receiver hosts and UDP port number for
Trap-Rec-Address
sending trap messages.
TrapReceiver
SNMP community string used for trap messages to the trap
Trap-Rec-Community
receiver.
Traps Trap types
Configuration status of trap message
Trap
Enabled - enabled : Trap message is allowed to send.
- disabled : Trap message is not allowed to send.
The table below describes the fields shown by the show snmp-server community-list
command output:
Field Description
The following is sample output from the show snmp-server statistics command:
The table below describes the fields shown by the show snmp-server statistics
command output:
Field Description
SNMP packets input Total number of SNMP packets received.
Bad SNMP version errors Number of packets with an invalid SNMP version.
Unknown community name Number of SNMP packets with an unknown community name
Illegal operation for Number of packets requesting an operation not allowed for that
community name supplied community
Encoding errors Number of SNMP packets that were improperly encoded
Number of requested
Number of variables requested by SNMP managers
variables
Number of altered variables Number of variables changed by SNMP managers
Get-request PDUs Number of get requests received
Get-next PDUs Number of get-next requests received
Set-request PDUs Number of set requests received
SNMP packet output Total number of SNMP packets sent by the router
Number of SNMP packets which were larger than the maximum
Too big errors
packet size.
Number of SNMP requests that specified an MIB object which does
No such name errors
not exist.
Number of SNMP set requests that specified an invalid value for an
Bad values errors
MIB object.
General errors Number of SNMP set requests that failed due to some other error.
Response PDUs Number of responses sent in reply to requests.
Trap PDUs Number of SNMP traps sent.
[en] show snmp-server user Showing snmp-server user information(only for v3)
To display the list of the trap receiver hosts, use the show snmp-server traphost
command in Privileged mode.
The following example shows how to display the list of the trap receiver hosts:
The table below describes the fields shown by the show snmp-server traphost command
output:
Field Description
host Protocol : IP address of a trap receiver host: port number.
Configuring RMON
RMON (Remote MONitoring) Overview
The RMON (Remote MONitoring) is an extend function of SNMP (Simple Network
Management Protocol) that designs to manage the devices from a remote place. The RMON
collects information that happens in a LAN segment such as the number of collision, packet size
distribution and amount of data in a distributed LAN environment, then the RMON delivers
information to managing device. The information can be used as resource to find out network
efficiency, collision, etc.
The RMON provides alarm function and event function that monitor the distributed LAN
environment and report changed status to users. Network problems can be easily solved by
network status report of RMON before network problem becomes worse.
RMON MIB groups consist of nine groups (1. Statistics 2. History 3. Alarm 4. Host 5. Host Top
N 6. Matrix 7. Filter 8. Packet Capture 9. Event), and the Corecess S5 System supports four
groups as follows:
Configuring RMON
The configuration procedure of RMON is as follows:
The RMON Alarm group allows you to set an alarm threshold and a sampling interval to
enable the RMON agent to generate alarms on any network segment it monitors. Alarm
thresholds can be based on ‘absolute’ or ‘delta’ values so that you can be notified of rapid spikes
or drops in a monitored value.
The alarm group periodically takes statistical samples from variables and compares them to
previously configured thresholds. The Alarm Table stores configuration entries that define a
variable, a polling period, and threshold parameters.
Each alarm is linked to an event in the event group. An event defines an action that will be
triggered when the alarm threshold is exceeded. The event generated when a RMON alarm
occurs should specify one of the RMON event entry and be configured. To configure the RMON
event, use rmon event command.
The alarm group retrieves variables periodically and compares variables to threshold. The
variable type, retrieval interval and threshold are consisted of an entry, and the entry is stored
in the alarm table.
To configure the RMON Alarm group, use the following message in Global configuration group.
Command Description
<index> Number to identify alarm group (1~ 65535)
<interval> MIB object monitoring interval (1-2147483647 seconds)
<type> Value to monitor. Select one of the following values:
- multicastPkts: The number of incoming multicast packets
- cRCAlignErrors: The number of incoming packets with CRC errors
- collisions : The number of times a collision occurs while the packet is
received
- octets: The total number of incoming octets
- pkts: The total number of incoming packets
- broadcastPkts: The number of incoming broadcast packets
- pkts256to511 : The number of incoming packets 256 to 511 bytes in
length
- pkts512to1023: The number of incoming packets 512 to 1023 bytes in
length
rmon alarm <index> - pktS54to1518 : The number of incoming packets 1024 to 1518 bytes in
<interval> {<type> length
<StatisticsIndex> - pkts64: The number of incoming packets 64 bytes in length
|<variable>} - pkts65to127: The number of incoming packets 65 to 127 bytes in
length
{delta | absolute}
- pkts128to255 : The number of incoming packets 128 to 255 bytes in
{rising | falling | length
both} threshold <StatisticsIndex> The number of statistics group to get the
<rising-threshold> selected value from <type>option (0 ~ 65535)
<falling-threshold> <variable> OID number of the MIB object to monitor
event-index <rising- absolute Option for testing each MIB variable directly
event-number> delta Option for testing the change between MIB variables
<falling-event-number> rising Option for triggering alarm when the monitored value
owner <alarm-owner> exceeds the rising threshold
falling Option for triggering alarm when the monitored value
exceeds the falling threshold
both Option for triggering alarm when the monitored value exceeds
the rising or falling threshold
<rising-threshold> Value at which the alarm is triggered (0 ~
2147483647)
<falling-threshold> Value at which the alarm is reset (0 ~
2147483647)
<rising-event-number> Event number to trigger when the rising
threshold exceeds its limit (0 ~ 65535)
<falling-event-number> Event number to trigger when the
falling threshold exceeds its limit (0 ~ 65535)
<alarm-owner> Option for specifying an owner for the alarm
The following example shows how to configure RMON alarm group and check the result:
# configure terminal
(config)# rmon alarm 1 10 pkts 1 absolute both threshold 1000 100 event-index 1
1 owner aaa
(config)#
Before configure RMON alarm group, you should verify that the statistics group
(<StatisticsIndex>) is defined.
If you specify undefined statistics group, the ‘Can’t fetch the MIB values’
message will be displayed:
To display the information on an alarm group, enter the show rmon command with the alarm
number:
# show rmon
RMON: Enabled
Extended RMON: Extended RMON module is not present
[statistics]
index status dataSource
----- -------------- -----------------------------
1 valid ifIndex.8 (Gi 1/1)
2 valid ifIndex.7 (Gi 1/2)
.
.
[history]
index status dataSource
----- -------------- -----------------------------
1 valid ifIndex.8 (Gi 1/1)
2 valid ifIndex.7 (Gi 1/2).
.
.
[alarm]
index status sample
----- -------------- -----------------------------
1 valid etherStatsPkts.1
[event]
index status type
----- -------------- ---------------
#
To display the detail information on an alarm group, enter the show rmon alarm command
with the alarm number:
To delete a RMON alarm group, enter the no rmon alarm command in Global configuration
mode:
The RMON Event group defines an action that is able to do when an alarm occurs. The action is
usually generating SNMP trap or storing the log entry to the log table to record the alarm. If
you configure SNMP trap generated, you should specify community to transmit the generated
trap to the managed system.
To configure the RMON Event group, use the following command in Global configuration
mode.
Command Description
<index> Number to identify events (1 ~ 65535)
description <string> Add a Description of the event.
- <string> A Description of the event.
rmon event <index>
trap <community> Option for generating SNMP trap with the
description <string>
<community> community string when the event occurs
{trap <community> |
- <community> Community String
log } owner <owner>
log Option for storing log for alarm when the alarm occurs
owner <owner> Option for specifying an owner for the event
- <owner> IP address, host name or user name
This example shows how to configure an event group on the Corecess S5 System and how to
verify that they are configured:
Parameter Value
Event index 10
Event Description Event to create log entry and SNMP notification
Event type log, trap
Community public
Owner help_desk
# configure terminal
(config)# rmon event 10 Description “Event to create log entry and SNMP
notification” log trap public owner help_desk
To display the information on an event group, enter the show rmon command:
# show rmon
RMON: Enabled
Extended RMON: Extended RMON module is not present
[statistics]
index status dataSource
----- -------------- -----------------------------
1 valid ifIndex.8 (Gi 1/1)
2 valid ifIndex.7 (Gi 1/2)
.
.
[history]
index status dataSource
----- -------------- -----------------------------
1 valid ifIndex.8 (Gi 1/1)
2 valid ifIndex.7 (Gi 1/2).
.
.
[alarm]
index status sample
----- -------------- -----------------------------
1 valid etherStatsPkts.1
[event]
index status type
----- -------------- ---------------
10 valid logandtrap
.
.
#
To display the detail information on an event group, enter the show rmon events command
with the event number:
To delete an event group, enter the no rmon event command in Global configuration mode:
In the Corecess S5 System, bandwidth information of traffic can be collected by RMON through
a particular port with a certain cycle (five seconds, one minute and ten minutes). To collect
bandwidth information communicated through the specified port, use the following commands.
Command Description
configure terminal 1. Enter Global configuration mode.
The following example shows how to collect the bandwidth information of traffic and verify it.
# configure terminal
(config)# rmon utilization
(config)# end
# show rmon utilization port gigabitethernet 1/3
Rx-avg: bits/s bytes/s pkts/s utilization
Tx-avg: bits/s bytes/s pkts/s
------------ ------------ ------------ -------------
Port 1/3
5 sec: 0 0 0 0
0 0 0
1 min: 0 0 0 0
0 0 0
10 min: 0 0 0 0
0 0 0
#
If you do not specify any option, the contents of the RMON alarm table, event table, history table, and
statistics table are displayed. The following is a sample output of the show rmon command:
# show rmon
RMON: Enabled
Extended RMON: Extended RMON module is not present
[statistics]
index status dataSource
----- -------------- -----------------------------
1 valid ifIndex.8 (Gi 1/1)
2 valid ifIndex.7 (Gi 1/2)
.
.
[history]
index status dataSource
----- -------------- -----------------------------
1 valid ifIndex.8 (Gi 1/1)
2 valid ifIndex.7 (Gi 1/2).
.
.
[alarm]
index status sample
----- -------------- -----------------------------
1 valid etherStatsPkts.1
[event]
index status type
----- -------------- ---------------
10 valid logandtrap
The table below describes the fields in the show rmon command output:
Field Description
The following example shows how to display the bandwidth information of traffic.
Command Description
show snmp-server Display SNMP configuration information of the system.
Show snmp-server
Display SNMP community list defined the system.
community-list
Show snmp-server statistics Display statistics information of SNMP operation.
Show snmp-server traphost Display list of trap host received trap.
Show rmon Display entry information of RMON table.
Snmp-server community Configure the SNMP community strings.
Snmp-server contact Specify the system operator information.
Snmp-server enable rmon Enable the RMON.
Snmp-server enable traps Enable a SNMP trap.
Limit hosts which can access to the system through SNMP based
Snmp-server group access
on the access list.
Snmp-server host Specify hosts to receive SNMP notifications.
Snmp-server location Specify the system location information..
rmon alarm Configure an RMON alarm group.
Rmon event Configures an RMON event group.
Rmon port Collects the average bandwidth information of traffic.
This chapter describes how to configure QoS (Quality of Service) on the Corecess S5 System.
QoS Overview
QoS Overview
This section describes QoS (Quality of Service) and QoS features supported by the Corecess S5
System.
QoS consists of the Classifier and the Traffic manager. The Classifier classifies traffic, and the
Traffic Manager processes the classified traffic as follows:
Traffic Manager
The Classifier refers to a header of a received packet, and then decides the QoS level. The traffic
manager marks the QoS level to the packet header or processes a packet that is in permitted
bandwidth. The Traffic Manager also chooses which packet drop when congestion occurs or
prefers which packet transmits first.
The following section describes parameters to classify packets and how to classify packet.
Classifier
Classification Standard
The classifier uses the following values to decide the packet level.
Layer 2 : Source/Destination MAC Address, EtherType Field, DSAP Field, 802.1P Field, VLAN ID
802.1P field in Layer 2 packet is a three bit field that marks the packet priority, and a number
from zero to seven is stuffed in the three bit field.
The following values are set in the eight bit of TOS field – also called DSCP field – in the
header of Layer 3 packet.
6 7
IP Type of Service (RFC 1349) IP DiffServ Code Point (RFC 2474)
bits bits 0 1 2 3 4 5 6 7
0 1 2 3 4 5 6 7
DSCP C
IP-Prec TOS MRZ U
Class Selector
D T R C
The classifier can classify the following types of category with the classification standard.
Subscriber and Application Classification: Who send the packet? And, what kind of application packet is?
- Packet Classification using Input Port Number, Source MAC Address, Source IP Address
and TCP/UDP Port Number
Subscriber and Destination Classification: Who send the packet. And, who receive the packet?
- Packet Classification using Input Port Number, Source MAC Address, Source IP Address,
Output Port Number, Destination MAC Address and Destination IP Address
Subscriber, Destination and Application Classification; Who send the packet?, Who receive the packet? And, what
kind of application packet is?
- Packet Classification using Input Port Number, Source MAC Address, Source IP Address,
Output Port Number, Destination MAC Address and Destination IP Address and
TCP/UDP Port Number
Classification Table
The classifier has two types. One is MF (Multi Field) classifier that refers several fields of a
packet simultaneously and decides QoS service level. The other is BA (Behavior Aggregate)
classifier that recognizes the packet decided QoS level.
MF classifier uses the following table to decide QoS level and to recognize a QoS profile.
Source Destination
Input Output Source Destination VLAN Source Destination Protocol TCP QoS
Rule# 802.1P TOS TCP/UDP TCP/UDP
Port # Port # MAC MAC ID IP IP ID Flag Profile
Port # Port #
1
2
3
4
5
6
7
.
.
.
A QoS profile has information what actions (marking, policing and assigning queue) should be
done to the packet decided QoS level through classification standard. The traffic manager
actually applies the actions to the packet.
Source Destination
Input Output Source Destination VLAN Protocol TCP QoS
Rule# 802.1P Source IP Destination IP TOS TCP/UDP TCP/UDP
Port # Port # MAC MAC ID ID Flag Profile
Port # Port #
1
2
3
4 * * * * 0x0800 * 1.1.1.0/24 20.1.1.0/24 6 * * 80 *
5
6
The BA classifier recognizes the QoS profile, which is applied to the packet, using the tables of
802.1p or ToS field that are only used for QoS. In the table of 802.1p or ToS field, the following
field values are defined. One of the profiles is applied to the packet by the field values.
TOS/DSCP/IP-Prec
802.1p Table
Table
802.1p Field Value QoS Profile ToS Field Value QoS Profile
0 0
1 1
2 2
3 3
4 4
5 5
6 …
7 255
Packet Marker
Packet marker marks 802.1P field or ToS field with QoS level. QoS level of a packet can use the
value decided by the classifier or be changed by QoS profiles. It is called “remarking” that the
first decided level is changed and marked by QoS profiles.
Policer
Policer can limit bandwidth to make users only use engaged traffic. Policer measures traffic
flow rate by traffic flow, which classified by classifier, and limits traffic not to use over engaged
bandwidth.
Policer consists of metering and action block. Metering measures traffic flow rate and compares
the result of traffic flow rate to engaged bandwidth, then informs the comparing result to action
block. Action block decide how to process traffic depending on the result.
Policer Variables
EBS
time
Token Bucket
There are several implementation of policer function, and the typical implementation is the
token bucket. The token bucket contains tokens, each of which can represent a unit of bytes.
Token is filled up in the token bucket for a certain rate. When packets are arrived, the same
amount of tokens is removed from the token bucket.
The variables of policer can be substituted for the element of token bucket as follows:
If tokens are full in the token bucket, no token is provided. When packets are received, the same
amount of token are removed. If the number of tokens is less than size of a packet, the packet is
specified as non-conforming packet. And, if the number of tokens is more than size of a packet
or is the same as the size of packet, the packet is specified as conforming packet. The packet
specified as non-conforming packet is processed by QoS profile of the packet.
There are two method of token bucket – single token bucket, dual token bucket. Single token
method uses only one bucket, and dual token method uses two bucket.
In dual token bucket method (RFC 2698 tr-TCM algorithm), the first bucket receives tokens at PIR
rate and the second bucket receives tokens at CIR rate. The first bucket size also is PBS and the
second bucket size is CIR. A packet that is specified as non-conforming in the first bucket finally
becomes the non-conforming packet. If a packet that is specified as conforming in the first bucket
becomes non-conforming in the second bucket, the packet is specified as loosely non-conforming
packet.
Dual token bucket method can control the packet with detailed classification above.
The following graph shows the dual token bucket method.
Queue Scheduler
The output port is generally slower than the input port because the output port transmits
packets that are received from the several input ports. In the output port, at least one queue is
assigned, and packets that have to be processed by the output port are saved. When saved
packets in a queue are more than bandwidth that can transmit packets – it means congestion,
what packets are transmitted first should be defined in the output port. This is called queue
scheduling.
There are various queues scheduling method, and the following methods are generally used.
In this method, each queue has assigned priorities (high, medium, low), and packets in the high
priority queue are transmitted first. After packets in the high priority are transmitted
completely, packets in the next priority queue are transmitted.
400B 500B 500B 400B 300B 600B 400B 500B 500B 200B 300B 400B 100B 300B
This method is easy to implement, but if there are plenty of packets that flows into the high
priority queue, packets in the low priority queue cannot be transmitted at all. This is called
starvation.
WRR method processed every queue in sequence to remove starvation that happens in SPQ
(Strict Priority Queuing). The packet size that process packets each time can be set for each
queue instead. A value, called weight, is used to set the packet size. The weight represents the
ratio of packets that is serviced through the queues.
[Q1] Weight: 2
200B 300B 400B 100B 300B
If weight values (2, 1, 1) are assigned to each queue as above, the ratio of packets are 2:1:1. It
means that two packets are transmitted through the first queue (Q1), and a packet is
transmitted through the second queue (Q2), then a packet is transmitted through the third
queue (Q3).
WRR method can specify priority to each queue and prohibit starvation as above. The
disadvantage of WRR is not useful in IP network that packet size is variable because weight is
ratio of packets. For example, there are two packets. One is 64byte VoIP packet, and the other is
1500byte data packet. The packets are serviced through two queues that weight is 2:1. Even
though the VoIP packet is serviced through high weight queue, 128bytes are sent each time, but
the 1500byte data packet can be sent through the low weight queue.
WFQ method divides whole packet in queue into bit unit to solve the problem of WRR and
transmits the bits at weight ratio of queues, then reassembles the bits.
400B 400B 500B 300B 200B 600B 300B 500B 400B 100B 300B
Output Port
This method can transmit packets without the packet size at the ratio that is specified in the
queue, but it is complicated to implement.
DWRR method enhances disadvantage of WRR and WFQ. DWRR defines weight, quantum and
deficit counter to each queue. Quantum is the maximum packet size that is processed by weight
ratio. Deficit counter is set to ‘0’ by default. Deficit counter is merged with quantum when data
of a queue is serviced. The packet of queue can be serviced up to deficit counter. After the
packet is serviced, deficit counter is decreased to the packet size.
For example, there is a queue that quantum value is 1000bytes. If 500byte packet, 300byte
packet, and 300byte packet are in a queue, only 500byte packet and 300byte packet can be
processed because the queue can process up to 1000bytes. Then, deficit counter becomes 200.
After other queues process their packet, the queue become in the order. The deficit counter
value becomes 1200, and the queue can process up to 1200byte.
Deficit counter memorizes the size of packet that was not transmitted as the ratio of weight, and
transmits the packet next time.
Let’s look at the operation principal of DWRR. There are three queues in an output port as
below. In each queue, 2:1:1 of weight is assigned. The quantum values of each queue are set as
1000byte, 500byte and 500byte. The deficit counter values are set as ‘0’ (Picture 1).
[Picture 1] [Picture 2]
The DWRR scheduler visits the number 1 of queue, then deficit counter value becomes
1000bytes. 300byte, 100byte and 400byte packets are transmitted through output port. After the
transmission, the deficit counter value becomes 200 (Picture 2).
The DWRR scheduler visits the number 2 of queue. The number 2 of deficit counter set the
value as 500byte, then 500byte packet is transmitted. After the transmission, the deficit counter
value becomes 0. The next time the number 3 of queue should be processed, but the first packet
in the number 3 of queue is 600byte and is bigger than deficit counter of 500byte. In this case,
deficit counter is not changed, and no packet is transmitted.
The DWRR scheduler visits the number 1 of queue again, then the quantum value is added to
the current deficit counter value. In this time, the deficit counter value becomes 1200bytes, and
the number 1 of queue can transmit packets up to 1200byte. 300byte and 200byte packets can be
transmitted, then deficit counter becomes 700 (Picture 3).
[Q1] Weight: 2
1200B - 300B - 200B [Q1] Weight: 2
Quantum=1000, DeficiCounter=700B Quantum=1000, DeficiCounter=0B
[Picture 3] [Picture 4]
There is no packet in the number 1 of queue, so the DWRR scheduler visits the number 2 of
queue. The deficit counter is set as 500byte, and 500byte packet is transmitted in the number 2
of queue, then deficit counter becomes 0. In the num 3 of queue that could not transmit packets
previous time, the deficit count becomes 1000byte, and 600byte and 300byte packet are
transmitted. After the transmission, the deficit counter becomes 100 (Picture 4). The rest of
packets are processed as above.
Shaping
Shaping is a function that limits bandwidth with buffering when traffic that is bigger than
target traffic rate flows into a queue.
The traffic that is more than target traffic rate is stored into the buffer. If there is enough
bandwidth to transmit, the stored traffic is transmitted.
This method is more flexible than policing, but is not useful in real-time traffic such as voice
traffic because transfer delay occurs.
WC scheduler can use whole bandwidth of output port until congestion occurs. SPQ, WRR,
DWRR and WFQ are WC method. On the other hand, even if there is no congestion, NWC
scheduler does not service more than bandwidth that is assigned queue. Shaping is this method.
Buffer Manager
Queues of an output port have fixed size. If a queue is full of packets, and other packets flow
into the queue, the packets are discarded as a particular rule. Buffer manager is the function
that discards received packets selectively to solve the congestion of the queue.
This section introduces that buffer manager methods.
Tail Drop
This section describes QoS features supported by the Corecess S5 System. The following figure
shows QoS structure on the Corecess S5 System:
Output
Q0 port #1 TC #1
Q1 TC #1
.
.
TC #1
Q6
Classifier
Input port #1 Q7
match
match
. .
. match .
. . .
.
.
.. .
.
Input port #n . .
.
.
Output
Q0 port #n
Q1
.
. TC #216
Q6 TC #217
Q7 TC #218
The Corecess S5 System classifies the packets from ingress (incoming) port according to the
criteria defined the class map, stores the classified packets to each transmit queue (0 ~ 7), and
transmits packets via TC (Traffic Class) applied the QoS action defied the policy map.
Packet Classification
The Corecess S5 System uses the values in the following fields of the layer 1 ~ layer 4 IP packet
header as a criterion to classify packets:
Layer 2: Source/destination MAC address, EtherType field, DSAP field, 802.1P filed, VLAN ID
The Corecess S5 System supports marking based on the following bits in the CoS (Class of
Service) filed for the packet:
DSCP
CoS
VLAN priority
The Corecess S5 System can recognize packets from a particular VLAN or port and configure
packets to set the specified values to the CoS field of packets.
Policing
The Corecess 5242 supports Policing. Policing is the process by which the system limits the
bandwidth consumed by a flow of traffic. You can limit the bandwidth of a specific traffic flow
by using a policy map or limit the full bandwidth of a port.
Transmit Queue
The Corecess S5 System provides eight transmit queues for each egress port. These transmit
queues are scheduled by the Strict Priority Queuing (SPQ) mechanism. The priority of queues
decides which queue transmits packets. The following values can be used as the priority, and
the user can specify which value uses as the priority.
VLAN Priority
Class Priority
When the transmit queue is full, frames at the end of the queue are dropped (tail drop)
Shaping
The first task for configuring QoS service policy is defining class
Defining Class Map maps.Class map defines a standard to classfy a particular traffic and
executethe role of QoS classifier.
The second step for configuring QoS service policy is defining policy
Defining Policy Map maps. Policy map defines QoS action that is applied to classified
traffic and execute the role of traffoc manager.
The last step of configuring the QoS Service policy is defining service
Applying
policies. A service policy consists of a policy-map and ingress/egress
Service Policy
ports which the policy map will be applied to.
You can classify packets and assign them to specific queues based on the following criteria:
CoS field cannot be included with DSCP or IP precedence in the same class-map.
After creating class-maps, system checks the inbound or outbound packets by the criteria in
class-maps. QoS actions defined in the policy-map for the class will be applied to the classified
packets into classes.
To create a class map and specify the way in which the Corecess S5 System should classify
traffic, enter the following commands in Global configuration mode:
Command Description
qos 1. Enter QoS configuration mode.
Class-map 2. Create a class map and enters class-map
<class-map-name> configuration mode.
Match any
match cos <value>
match dsap <value>
match dscp <value>
match ether-type <value>
match fragment-bit <value>
match input-port <port-type>
<slot>/<port>
match ip-da <destination-ip> <mask>
match ip-prec <value>
match ip-sa <source-ip> <wildcard>
match mac-da <destination-mac>
3. Define the classification criteria for the class map.
match mac-sa <source-mac>
match output-port <port-type>
<slot>/<port>
match protocol <protocol field>
match ssap <value>
match tcp-dpn <tcp-port-num>
match tcp-flag <flag-num>
match ttl <value>
match udp-dpn <udp-port-num>
match ucp-spn <udp-port-num>
match vlan-sid <vlan-id>
match vlan-did <vlan-id>
End 4. Return to the Privileged mode.
Show classmap <class-map-name> 5. Verify the class map configuration.
The following example shows how to create a class map and define a classification criterion by
using the source IP address:
(config)# qos
(config-qos)# class-map class1
(config-cmap)# match ip-sa 172.27.2.16 0.0.255.255
(config-cmap)# end
# show classmap
ClassMap
Name : class1
Match Content : ip-sa 172.27.2.16/0.0.255.255
Total Entries = 1
The following example shows how to create a class map and define the criteria by using the
destination IP address and the destination TCP port number:
(config)# qos
(config-qos)# class-map class2
(config-cmap)# match ip-da 10.10.10.1 0.0.0.255
(config-cmap)# match tcp-dpn 25
(config-cmap)# end
# show classmap class2
ClassMap
Name : class2
Match Content : ip-da 10.10.10.1/0.0.0.255
: tcp-dpn 25
Total Entries = 2
#
that have different classification and QoS actions that are applied to the classes. And, several
policy maps can be applied to an interface. Each policy map should be applied to different types
of traffic.
To apply multiple QoS actions to a traffic class, multiple QoS actions can be included in a
policy-map.
Creating a Policy-map
To create a policy-map and configure QoS actions for a traffic class, perform this task:
Command Description
qos 1. Enter QoS configuration mode.
62. Create a policy map and enter the policy-
map configuration mode.
Policy-map <policy-map-name>
<policy-map-name>: Name of
a policy map to define.
3. Specify the class to which the policy map applies and
Class <class-name>
enter the policy-map-class configuration mode.
Filter {deny|logging
|permit|to-proc}
4. Configures QoS actions for the class. Refer to the 메모 [zwyi3]: logging 추가
mark {cos|dscp|ip-prec} <value>
following sections for configuring QoS actions in the
priority <value>
policy-map class configuration mode.
rate-limit rate <value>
The following example shows how to create a policy map and specify a class map to which the
policy map applies:
(config)# qos
(config-qos)# policy-map policy1
(config-pmap)# class class1
(config-pmap-c)# priority 7
(config-pmap-c)# end
# show policymap policy1
PolicyMap
Name : policy1
Linked ClassMap : class1
Policy : priority 7
Total Entries = 1
#
The QoS fields such as the Layer 2 CoS (802.1p field) or Layer 3 IP precedence, ToS, or DSCP
fields are used for classifying the traffic class. Depending on the network state or QoS policy,
user can set these fields to the specified values which can change the priority of traffic.
To set the QoS fields of packets, which belong to the policy-map class to the specified values,
perform this task in the Policy map class configuration mode.
Table 8-5 Changing CoS, IP Precedence, or DSCP value of a traffic class in a policy map
Command Description
qos 1. Enter QoS configuration mode.
63. Create a policy map and enter policy-map configuration
Policy-map
mode.
<policy-map-name>
<policy-map-name>: The name of a policy-map.
64. Specify the class to which the policy map applies and enter
policy-map-class configuration mode.
Class <class-name>
<class-name>: The name of the class to which the policy map
applies.
65. Specify the value and type of the field to change.
cos <value>: Specify the value of the CoS field (0 ~ 7).
Mark {cos | dscp |
dscp <value>: Specify the value of the DSCP field. (0 ~ 64).
ip-prec} <value>
ip-prec <value>: Specify the value of the IP precedence field(0 ~
7).
This example configure remarking feature to set the CoS field to “7” of the traffic class class3 in
the policy map polmap6:
(config)# qos
(config-qos)# policy-map polmap6
(config-pmap)# class class2
(config-pmap-c)# mark cos 7
(config-pmap-c)#
In a policy-map, you can add criteria for filtering a traffic class or forwarding it to the internal
system processor.
To add a criterion for deciding whether filtering packets or forwarding, perform this task.
Command Description
qos 1. Enter QoS configuration mode.
66. Create a policy map and enter policy-map
Policy-map <policy-map-name> configuration mode.
<policy-map-name>: The name of a policy-map.
67. Specify the class to which the policy map applies
and enter policy-map-class configuration mode.
Class <class-name>
<class-name>: The name of the class to which the policy
map applies.
68. Select the filtering method of the traffic class.
Filter deny: Discard the traffic.
{deny|permit|to-proc} permit: Forward the traffic.
to-proc: Send the traffic to the CPU.
This example configures to discard the traffic class class2 in the policy map polmap6:.
(config)# qos
(config-qos)# policy-map polmap6
(config-pmap)# class class2
(config-pmap-c)# filter deny
(config-pmap-c)#
The priority command in the policy-map configuration mode can assign the user-defined
priority to a traffic class. This user-defined priority is used for selecting one of eight
transmission queues in an output port for buffering packets. It is also used as the value for CoS
field. By default, a transmission queue is select by this user-defined priority. However, you can
use the CoS, DSCP, or VLAN ID when selecting a transmission queue. To do this, use the
queue-precedence command in the QoS configuration mode.
The following is a procedure for specifying the user-defined priority for a traffic class:
Command Description
qos 1. Enter QoS configuration mode.
Policy-map 69. Create a policy map and enter policy-map configuration
<policy-map- mode.
name> <policy-map-name>: The name of a policy-map.
70. Specify the class to which the policy map applies and enter
Class <class- policy-map-class configuration mode.
name> <class-name>: The name of the class to which the policy map
applies.
71. Gives priority to a class of traffic belonging to a policy-map.
Priority
<value>: Priority (0 ~ 7). ‘0’ is the lowest priority queue and ‘7’ is the
<value>
highest priority queue.
This example assigns the queue with the priority of 7 to the traffic class class4 in the policy map
polmap6:
(config)# qos
(config-qos)# policy-map polmap6
(config-pmap)# class class4
(config-pmap-c)# priority 7
(config-pmap-c)#
In a policy map, you can configure the rate limiting feature which discards the packets that
exceed the bandwidth limits.
Rate limiting is the process by limiting the bandwidth consumed by a flow of traffic. After a
packet is classified, the rate limiting process can begin. The rate limiting involves creating a
policer that specifies the bandwidth limits for the traffic. Packets that exceed the limits are
dropped.
To configure the rate limiting feature in a policy map, perform this task in the Global
configuration mode:
Command Description
qos 1. Enter QoS configuration mode.
Policy-map 72. Enter policy-map configuration mode.
<policy-map-name> <policy-map-name>: The name of a policy-map.
73. Specify the class to which the policy map applies and enter
policy-map-class configuration mode.
Class <class-name>
<class-name>: The name of the class to which the policy map
applies.
74. Establish target bandwidth to apply Policy.
Rate-limit rate
<target-rate> : input target bandwidth by 64 Kbpses (0 ~
<target-rate>
1000000, Kbps) .
bucket <bucket>
<bucket> : Input bucket size (dimension : bytes)
메모 [zwyi4]: we delete
Note: Policing can be applied to a specific port as well as a specific traffic class. Entering description of unit.
the rate-limit command in the QoS configuration mode specifies the target bandwidth to be
applied to both incoming and outgoing traffic through a port. How to configur e policing for a
port will be described later in this chapter.
This example specifies the target bandwidth of the traffic class class5 to apply the rate limiting
in the policy map polmap6:
(config)# qos
(config-qos)# policy-map polmap6
(config-pmap)# class class2
(config-pmap-c)# rate-limit rate 640
(config-pmap-c)#
Defining class map and policy map is a process to make rules for QoS. On the other hand,
defining service policy is a process to select which rule is applied and which port uses the rule.
Command Description
qos 1. Enter the QoS configuration mode.
Service-policy <service-name> 75. Define service policy.
policy-map <policy-map-name> <service-name> Name of the service map.
[input-port gigabitethernet <policy-map-name> Name of the policy map.
<slot>/<port>] [output-port input-port Attach the policy map to input traffic.
gigabitethernet output-port Attach the policy map to output traffic.
<slot>/<port>] <slot>/<port> Slot number and port number
end 3. Return to the Privileged mode.
Show service-policy
4. Verify the service policy configuration.
[<service-policy-name>]
Note: Defining service policy, you can allocate aggregated ID to the specified port. In other
words, Between 1/1 port and 1/2 port in LACP, you can apply QoS rules not to 1/2 port but
to 1/1 port, the representative port between two ports . Naturally, rules applied to 1/1 can be
also applied to 1/2 port. And QoS rules before LACP is no more valid. However, in the
moment that the ports are free from LACP, the previous rules will be just applied. To
comprehend more detailed Description, confirm chapter.14 LACP Configuring.
This example applies the policy map named ‘polmap6’ to the Gigabit Ethernet port 17/1 and
verifies the configuration:
(config)# qos
(config-qos)# service-policy service1 policy-map polmap6 input-port gigabitethernet 17/1
(config-qos)# end
# show service-policy
ServicePolicy
Name : service1
Linked PolicyMap : polmap6
Port(In ) : 17/1
Port(Out) : 17/1
Total Entries = 1
#
Command Description
config 1. Enter configuration mode.
Command Description
qos 1. Enter QoS configuration mode.
The following example shows how to discard excess packets when broadcast packet is received
more than 256 per a second.
(config)# qos
(config-qos)# broadcast-storm-control vlan id 1 pps 256
(config-qos)#
Packet Filtering
If a host who is connecting to a Corecess S5 System runs a private DHCP server, other
subscribes connected with the Corecess S5 System may receive an invalid IP address from that
private DHCP server. To prevent this, you can filter DHCP Offer packets received from a host.
Internet or LAN
Corecess S5 System
Filter DHCP Offer packets received
from the DHCP server of ONU
Command Description
qos 1. Enter QoS configuration mode.
78. Filter DHCP server packet received to the specified
port. If a port is not specified, all port of the system are
Dhcp-offer filter discard filtered.
[port gigabitethernet
<slot>/<port>] accept Allow receiving DHCP server packet.
discard Discard receiving DHCP server packet.
<slot>/<port> Slot number and port number
end 3. Return to the Privileged mode.
4. Display the ports configured to filter the DHCP packets received
Show dhcp-offer-filter
from hosts..
The following example configures to discard all the DHCP OFFER packets received from the all
the ports:
(config)# qos
(config-qos)# dhcp-offer filter discard
(config-qos)# end
# show dhcp-offer-filter
Dhcp Offer Filter Ports
Accept :
Discard : All Ports
#
To prevent hosts that are connected on the same VLAN from sharing files and resources, the
Corecess S5 System can filter protocols as follows:
Corecess S5 System
ONU
ONU
호스트 호스트
Host Host
To filter the packet of file and resource sharing protocol, use the following commands.
Command Description
qos 1. Enter QoS configuration mode.
2. Set to deny receiving particular protocol packets.
Apple-filesharing-protocol 2-1. Refuse Apple FileSharing packets. This command is applied
filter discard to all ports.
Netbios filter discard
2-2. Refuse NetBIOS packet received to the specified port.
[port gigabitethernet
<slot>/<port> Slot number and port number
<slot>/<port>]
2-3. Refuse Rendezvous packets. This command is applied to all
rendezvous filter discard
ports.
Upnp filter discard 2-4. Refuse UpnP packets. This command is applied to all ports.
End 3. Return to Privileged mode.
Show running-config 4. Verify the filtering configuration.
The following example shows how to filter the file and resource sharing protocols received to
all ports.
(config)# qos
(config-qos)# apple-filesharing-protocol filter discard
(config-qos)# netbios filter discard
(config-qos)# rendezvous filter discard
(config-qos)# upnp filter discard
(config-qos)# end
# show running-config
.
.
!
qos
default traffic deny
shaping output-port gigabitethernet 17/1 rate 128000
netbios filter discard
rendezvous filter discard
apple-filesharing-protocol filter discard
upnp filter discard
!
.
.
Default traffic is traffic that is not classified with defined class map in the Corecess S5 System. If
default traffic is filtered, traffic that is not specified by network operators is discarded, so it can
prevent traffic that is not permitted from receiving.
Command Description
qos 1. Enter QoS configuration mode.
The following example shows how to refuse default traffic that is not classified with class map.
(config)# qos
(config-qos)# default traffic deny
(config-qos)# end
# show default-traffic-policy
Default QoS Traffic Policy
Deny
#
The Corecess S5 System can filter broadcast packets that are transmitted from a particular port.
It prevents unnecessary broadband packets from transmitting.
Command Description
qos 1. Enter QoS configuration mode.
Egress-filter broadcast 79. Discard broadcast packets from a particular port on the
vid <vlan-id> port specified VLAN.
gigabitethernet <vlan-id> VLAN ID (1 ~ 4094)
<slot>/<port> <slot>/<port> Slot number and port number
end 3. Return to Privileged mode.
The following example shows how to filter broadcast packet on the Gigabit Ethernet port 17/1.
(config)# qos
(config-qos)# egress-filter broadcast vid 1 port gigabitethernet 17/1
(config-qos)#
This chapter describes how to configure DHCP server or DHCP relay agent.
DHCP (Dynamic Host Configuration Protocol) Overview
DHCP has client-server architecture. A DHCP server is generally located in central place, and is
operated by network operators. DHCP server can receive reliable and appropriate information
for the current network status because of network operators.
Most of network consists of several subnets called VLAN. Each VLAN should basically have a
DHCP server because packets are only broadcasted in internal VLAN. If a VLAN has not a
DHCP server, it should be configured that the VLAN supports the DHCP relay agent feature.
DHCP clients and DHCP servers request and transmit information using DHCP messages. The
following figure shows the basic steps that occur when a DHCP client requests an IP address
from a DHCP server.
1. DHCPDISCOVER
2. DHCPOFFER
3. DHCPREQUEST
4. DHCPACK
80. DHCPDISCOVER
A DHCP Client broadcasts the DHCPDISCPVER message to local network for searching a
DHCP server.
81. DHCPOFFER
If there is a DHCP server in the local network, the DHCP server, which receives the
DHCPDISCOVER message, transmits the DHCPOFFER message with DHCP configuration
parameters (IP address, MAC address, domain name and assigned time of IP address).
82. DHCPREQUEST
When the DHCP client, which transmitted DHCPDISCOVER message, receives the
DHCPOFFER message, the DHCP client transmits the DHCPREQUEST message to
requests that the client uses the received parameters.
83. DHCPACK
When the DHCP server receives the DHCOREQUEST message, the DHCP server transmits
the DHCPACK message to approve that the client can use the assigned IP address.
84. DHCPRELEASE
When lease time of IP address that the DHCP client uses is over, or the DHCP client is shut
down, the DHCPRELEASE message is transmitted.
Configure DHCP Server Parameter to be allocated when allocating the IP of corresponding Pool in IP Pool; and
Values to be identified
Corecess S5 configures DHCP Server by VLAN unit. To configure DHCP Server, below-listed
values should be identified in advance:
Range of IP to be allocated;
Various network information including the gateway address to be used by the Host to which IP was
allocated; and
IP lease time.
Command Description
configure terminal Enter into Configuration mode.
Interface vlan id [id] Enter into Interface mode.
Ip dhcp server Enable DHCP Server.
End Return to Privileged mode.
Show ip dhcp interface Check the activation of DHCP Server.
To disable DHCP Server so as not to act anymore, run no ip dhcp server command in Interface
Mode.
Below-shown are the kinds and default values of parameters supplied by DHCP in Corecess:
These DHCP Parameters may set distinguishing into Global mode applied to all the subnet and
IP Pool mode applied to only one subnet.
If the setting is done to both Global mode and IP Pool mode, the value set in IP Pool mode is
firstly applied in corresponding subnet.
The method to designate the parameter as the prior Global mode as shown below:
Command Work
configure terminal Enter into Global Configuration mode.
Ip dhcp leasetime <time> Designate Default lease allocation time.
Ip dhcp default-gateway <ip-
address> Designate default gateway.
Ip dhcp dns-server <ip-address> Designate the address of Dns-Server.
Ip dhcp log-server <ip-address> Designate the address of Log-Server.
Ip dhcp wins-server <ip-address> Designate the address of Wins-Server.
Ip dhcp merit-dump-file <string> Designate the route of Merit-dump-file.
Ip dhcp root-path <string> Designate the path of Root disk.
Localhost(config)#
To return the default lease time to default setting value, 43200, execute no ip dhcp leasetime
command.
Setting root-path
The path of root disk may be set as shown below:
Creating IP Pool
In IP Pool, Ips allocated to clients in DHCP Server and related parameters may be set. To do so,
IP Pool should be created in advance.
To create IP Pool, execute below-shown command.
Command Description
configure terminal Enter into Global Configuration mode.
Ip pool <string> Create IP Pool named <string>.
End Return to Privileged mode.
Show service-manager ip pool config Check created IP Pool.
Command Description
configure terminal Enter into Global Configuration mode.
Ip pool <string> Create and Enter into <string> pool.
Network <ip-address/mask> Set subnet.
Ip range dhcp <start-ip> <end-ip> or
IP range to be allocated is set.
ip range dhcp <ip-address/mask>
End Return to Privileged mode.
Show service-manager ip pool config Check pool setting.
The next is the example to set the IP range to be allocated to subnet in IP Pool.
To delete subnet and IP address range set in IP Pool, execute below-shown commands:
Ex)
When creating:
localhost(config-ippool)# ip range dhcp 50.1.1.2 50.1.1.254
When deleting:
localhost(config-ippool)# ip range dhcp 50.1.1.3 50.1.1.254 (X)
localhost(config-ippool)# ip range dhcp 50.1.1.2 50.1.1.250 (X)
localhost(config-ippool)# ip range dhcp 50.1.1.2 50.1.1.254 (O)
When creating:
localhost(config-ippool)# ip range dhcp 50.1.1.0/24
When deleting:
localhost(config-ippool)# no ip range dhcp 50.1.1.0/26 (X)
localhost(config-ippool)# no ip range dhcp 50.1.1.0/24 (O)
To exclude specific IP range from the allocation range, use below-shown commands:
Command Description
configure terminal Enter into Global Configuration mode.
Ip pool <string> Create and Enter into <string> pool.
Ip range excluded-address <start-ip> Set the IP Range to be excluded from allocation
<end-ip> range.
End Return to Privileged mode.
Show service-manager ip pool config Check pool setting.
Below-shown is the example to set the IP Range to be excluded from the allocation range in IP
Pool.
localhost#
Command Description
configure terminal Enter into Global Configuration mode.
Ip pool <string> Create and Enter into <string> pool.
Ip dhcp leasetime <time> Designate Basic lease allocation time.
Ip dhcp default-gateway <ip-
Designate basic gateway.
address>
Ip dhcp dns-server <ip-address> Designate the address of Dns-Server.
Ip dhcp log-server <ip-address> Designate the address of Log-Server.
Ip dhcp wins-server <ip-address> Designate the address of Wins-Server.
Ip dhcp merit-dump-file <string> Designate the route of Merit-dump-file.
Ip dhcp root-pathname <string> Designate the path of Root disk.
Localhost(config)#
To delete set WINS Server address, execute no ip dhcp WINS server command.
Setting root-path
The path of root disk may be set as shown below:
Five pools are connected to a single direction list by Pool Chaining method and Pool #1 at the
front is connected with interface.
When IP request is received from a client, IP is firstly allocated to Pool #1 at the left and then in
the order of Pool #2, Pool #3…
Below-shown is the commands to configure Pool Chaining.
Command Description
configure terminal Enter into Global Configuration mode.
Ip pool <string> Create and Enter into <string> pool.
Designate the next Pool to be connected by Pool
Next-pool <string>
Chaining.
End Return to Privileged mode.
Show service-manager ip pool
Check pool setting.
config
localhost(config-ippool)# exit
localhost(config)# ip pool pool4
localhost(config-ippool)# next-pool pool5
localhost(config-ippool)# exit
localhost(config)# ip pool pool3
localhost(config-ippool)# next-pool pool4
localhost(config-ippool)# exit
localhost(config)# ip pool pool2
localhost(config-ippool)# next-pool pool3
localhost(config-ippool)# exit
localhost(config)# ip pool pool1
localhost(config-ippool)# next-pool pool2
localhost(config-ippool)# exit
localhost(config)# interface vlan id 50
localhost(config-if)# dhcp address-pool local pool1
localhost(config-if)#
localhost(config-if)#
Command Description
configure terminal Enter into Configuration mode.
Interface vlan id [id] Enter into Interface mode.
Ip dhcp relay Enable DHCP Relay.
In case of DHCP Relay also, like DHCP Server, activation by interface unit is possible. The
interface to be Enabled is the one that belongs to the network where the client to receive IP
through DHCP exists.
Command Description
configure terminal Enter into Global Configuration mode.
Interface vlan id <id> Enter into Interface mode.
Ip dhcp helper-address <ip-address> Set External DHCP Server Address.
End Return to Privileged mode.
Below-shown is the example to designate DHCP Server to send/receive Packets to/from DHCP
Relay.
DHCP Relay unicasts Packets to DHCP Server designated by above-shown commands every
time when the DHCP packet broadcasted by client is received.
However, sometimes DHCP Server cannot allocate IP to multiple subnets of an interface. The
purpose of DHCP Secondary weight function is to support IP allocation connected with such
DHCP Server.
To allocate corresponding IP to each subnet, weight should be given to the interface Ips
(secondary Ips) corresponding to each subnet excluding the first subnet.
To give weight to secondary Ips, execute below-shown commands:
Command Description
configure terminal Enter into Global Configuration mode.
Interface vlan id <id> Enter into Interface mode.
Ip dhcp secondary weight
<ip-address> <weight> <total> Set weight to secondary Ips.
In the commands to give weight to secondary Ips, <total> means the whole ratio of Ips for
allocation and <weight> means the ratio of IP allocated to the subnet corresponding to
secondary IP.
Below-shown is the example of such command.
Command Description
configure terminal Enter into Global Configuration mode.
Interface vlan id <id> Enter into Interface mode.
Ip dhcp proxy-server Enable DHCP Proxy Server in interface.
End Return to Privileged mode.
Localhost#
localhost# configure terminal
localhost(config)# interface vlan id 50
localhost(config-if)# ip dhcp proxy-server
Sep 28 15:51:30 localhost DHCP-7-INFO: DHCP Proxy Server serviced on interface
v
lan50.
Localhost(config-if)# end
localhost# show ip dhcp interface
Command Description
configure terminal Enter into Global Configuration mode.
Interface vlan id <id> Enter into Interface mode.
Ip dhcp proxy helper-address <ip-address> Set External DHCP Server Address.
End Return to Privileged mode.
localhost#
localhost#
localhost#
Command Description
dhcprelay Enables the DHCP relay agent on the Corecess S5 System.
Dhcprelay security Enables the DHCP relay security feature.
Adds the DHCP servers which will assign the IP address to the DHCP
Dhcprelay serverlist
relay.
Dhcpserver bootp Allows for the DHCP server to respond to the BOOTP queries.
Specifies the global default Domain Name System (DNS) server which
Dhcpserver defaultdns
applies to all the DHCP subnets.
Dhcpserver
Specifies the global default gateway list for all the DHCP subnets.
defaultgateway
Dhcpserver Specifies the duration of the lease for an IP address that is assigned from
defaultleasetime a DHCP server to a DHCP client.
Dhcpserver Enables the DHCP server on the Corecess S5 System.
Dhcpserver host Specifies the IP address for a manual binding to a DHCP client.
Specifies a log server to which logging information DHCP clients are
Dhcpserver log-server
sent.
Dhcpserver
Specifies the upper limit of the default lease time.
maxleasetime
Specifies the path name of the merit dump file to which the client’s core
Dhcpserver merit-dump
image should be placed in the event the client crashes.
Dhcpserver root-path Specifies the path name that contains the client’s root disk.
Dhcpserver security Enables the DHCP server security feature.
Adds a DHCP subnet. The clients in the DHCP subnet can be assigned
Dhcpserver subnet
the IP addresses from the DHCP server.
Dhcpserver subnet
Specifies the default Domain Name System (DNS) server for a subnet.
defaultdns
Dhcpserver subnet
Specifies the default gateway list for a subnet.
defaultgateway
Specifies the duration of the lease for an IP address that is assigned to the
Dhcpserver subnet
DHCP clients in a subnet. This value will apply to the specified DHCP
defaultleasetime
subnet.
(Continued)
Command Description
dhcpserver subnet
Specifies the high-threshold of the number of the leased IP addresses.
highthreshold
Dhcpserver subnet Sets the range of addresses (or address pool) for DHCP clients in the
iprange specified subnet.
Dhcpserver subnet Specifies a log server to which logging information DHCP clients are sent
log-server for a subnet.
Dhcpserver subnet
Specifies the low-threshold of the number of the leased IP addresses.
lowthreshold
Dhcpserver subnet
Specifies the upper limit of the default lease time for a subnet.
maxleasetime
Dhcpserver subnet Specifies the path name of the merit dump file to which the client’s core
merit-dump image should be placed in the event the client crashes for a subnet.
Dhcpserver subnet
Specifies the path name that contains the client’s root disk for a subnet.
root-path
Dhcpserver unicast Allows for the DHCP server to send unicast reply.
Dhcpserver Allows for the DHCP server to assign IP addresses to the unknown
unknownclien ts hosts.
Show dhcp statistics Shows the statistics of the DHCP
show dhcp version Shows the version of the DHCP module.
Show dhcprelay Shows the status of the DHCP relay agent
show dhcprelay Shows the list of the DHCP servers which assign the IP addresses to the
serverlist clients of the DHCP relay agent.
Show dhcpserver Shows the global DHCP server configuration.
Show dhcpserver host Shows the list of the static hosts who can get the fixed IP addresses.
Shows the current usage of the IP addresses available for the DHCP
Show dhcpserver lease
clients.
Show dhcpserver
Shows the DHCP subnet configuration.
subnet
In this chapter, the method to use the Netsnoop functions of Corecess S5 System is described.
Understanding NetSnoop
Understanding NetSnoop
In this chapter, the specific features of NetSnoop and the method to use are described.
Understanding NetSnoop
NetSnoop is the function to manage user’s profile and to protect users and equipment from
various wrong network attack with use of DHCP and ARP.
It consists of two modules: DHCP Snoop and ARP Snoop.
In general, this function is available when using L3 Gateway or L2 Switch.
DHCP Snoop
Differently from DHCP Server or Relay, it manage DHCP state machine to snoop DHCP Packet
and supports with security function for basic DHCP Packet. Also, when it interworks with ARP
Snoop, it may prevent illegal use of IP by the method to pass only the ARP Packet to which IP
was assigned through DHCP.
This is the filtering rule of whole S5 equipment. Two modes – Permit and Deny – are provided;
in case of Permit mode, control such as communication blocking is not performed. In contrast,
in case of Deny mode, the subscribers who were assigned with Ips through DHCP may only
communicate.
received by this Port and the Packets sent from Server are blocked. Also, if Base Rule is in Deny
status, the clients received Ips through DHCP may only communicate.
Transparent Port acts as a common port. In this port, all the hosts may communicate regardless
of Base Rule.
The thing to be done for the first time to configure DHCP Snoop is to Enable DHCP Snoop in
the Corecess S5 System by the method shown below:
Command Description
configure terminal 1. Enter into Global Configuration Mode.
Ip dhcp snoop 2. Enable DHCP snoop.
This is the basic value to permit communication to the users with assignment of Ips through
licensed DHCP and converts the System Base Rule set as Permit mode to Deny mode.
Command Description
configure terminal 1. Enter into Global Configuration Mode.
Ip dhcp snoop base-rule
deny 2. System Base Rule of DHCP snoop is converted into Deny mode.
The next is the example to set Base Rule of Corecess S5 System as Deny mode.
localhost#
Command Description
configure terminal 1. Enter into Global Configuration Mode.
Ip dhcp snoop port <port 2. Set corresponding port as Server Port. The port connected with
info> server DHCP Server is set as this one.
3. Set corresponding port as Transparent Port (basic value). In
Ip dhcp snoop port <port
info> transparent case of ports that do not need to or should not manage hosts are
set as theses ports.
4. Set corresponding port as Client Port. The ports that intend to
Ip dhcp snoop port <port
info> client permit the communication to the subscribers with assignment of
Ips through licensed DHCP are set as these ports.
Ip dhcp snoop port <port
info> client-limit <num> 5. Number of clients of corresponding port is limited to <num>.
Ip dhcp snoop port <port
info> circuit-id <str> 6. The Circuit-ID of corresponding port is set as <str>.
Ip dhcp snoop port <port
info> base-rule 7. The Base-Rule of corresponding port is set as Deny mode.
<permit|deny>
Ip dhcp snoop port <port 8. A host is set as static type so that a specific host may always
info> static <MAC> <IP> communicate in the corresponding port.
No ip dhcp snoop port <port
info> 9. Corresponding port should not use Netsnoop function.
When setting as transparent port, basic setting, again, execute ip dhcp snoop port <port info>
transparent command.
Below-shown is the example to execute the command.
Localhost# configure terminal
localhost(config)# ip dhcp snoop port fastethernet 3/1 transparent
localhost(config)#
Default
Parameter Description
value
When inputted Packet is not same with saved information,
Information policy Replace
whether to update is decided.
Inspection Appropriateness of inputted Packet is inspected. None
Broadcast is converted into Unicast with use of saved
Secure-unicast None
information.
Suppression Burst packet attack is blocked with use of DHCP Packet. None
The method to set the values of such DHCP snoop parameters are as follows:
Command Description
Ip dhcp snoop inspection 10-11thernet header and the mac address recorded in chaddr of
<mac-match|client-id| dhcp header is same.
state_transition>
<client-id> : It is inspected whether the mac address of
10-11thernet header and the mac address recorded in client-id of
dhcp header is same.
<state transition> : It is inspected whether inputted Packet is
appropriate DHCP Packet in terms of state.
4. The Packet, which is transferred to broadcast if corresponding
Ip dhcp snoop secure-
unicast client information exists when the Packet to be transferred to
client is inputted, is transferred to unicast.
87. When two or more Discover Packets are inputted
Ip dhcp snoop suppression from a same DHCP Client within the set time, the
<seconds> Packets other than the firstly inputted Discover
Packet are dropped.
To set so as to update saved information to the client information of newly inputted Packet,
execute ip dhcp snoop information policy replace command.
Below-shown is the example to execute the command.
Localhost# configure terminal
localhost(config)# ip dhcp snoop information policy replace
localhost(config)#
duplicated. If you do not want to use inspection function, execute no ip dhcp snoop inspection
command.
Below-shown is the example to execute the command.
Localhost# configure terminal
localhost(config)# no ip dhcp snoop inspection
localhost(config)#
Setting Option82
Below-shown is the command to add DHCP Option82 in DHCP Snoop.
Command Description
If you intend not to use Option82 function anymore, execute no ip dhcp snoop opt82 command.
Below-shown is the example to execute the command.
L2DhcpRelay
L2DhcpRelay is the function that relay DHCP packet to DHCP server in L2 Switch.
Usually, When there is no DHCP server to subnet with client that receive actual IP, it is that
'L2Dhcprelay' relay packet between DHCP client and DHCP server. Therefore, this function acts
in gateway. However, you should offer DHCP Relay function in L2 switch if it is situation that
operate each DHCP server because several subnets share single gateway mounting and ISP
exists in each subnet. In this case you need DHCP Relay function in L2 switch.
Command Description
[no] ip dhcp snoop l2-relay
To relevant vlan giaddr l2-relay that do <ip> action.
vlan id <id> gateway ip <ip>
[no] ip dhcp snoop l2-relay
To vlan that l2-relay is acting helper-address addition.
vlan id <id> helper-address <ip>
ARP Snoop
In case of existing LAN switch, the arp request used in linking ip address and mac address in
IPv4 is basically broadcasted. In this case, malicious user may easily obtain the ip/mac
information of other hosts of nodes on the LAN by sniffing the Packet with substitution of own
network device for promiscuous mode. Based on such information, the arp information of
router may be poisoned and the traffic of other hosts may be monitored. Also, by producing
wrong arp reply/request, proper users become ip conflict status and cannot receive network
service. To solve such problem, ARPsnoop blocks inputting of improper arp packet by
inspecting all the arp request/reply inputted into the switch and manages the ip/mac in the
table to reduce the quantity of broadcasted arp request .
When interworking with DHCPsnoop, arp request/reply is permitted only to the subscribers
using the ip-pool allocated through proper dhcp action and it can be prevented that malicious
user receives service by producing improper arp request or setting static IP.
Command Description
When the user communicates with use of proper IP, the entry is created and maintained in the
table managed by ARP snoop. Also, the users using static IPs set by group access list have static
entries. If you want to maintain the table of static IP users by maintaining the entries until the
users’ terminals are turned off, you may set ARP snoop active-probing and then ARP snoop
periodically transfers ARP request message to maintain the entries.
Command Description
Command Description
When performing arp secured with use of dhcp binding information, Deny and Permit may be
performed with referring to access-list only with no secure checking of IP existing in
corresponding access-list to manage the lower layer equipment using static IP.
Command Description
As improper ARP Snoop table may be configured when arp poisoning is detected by the
equipment where ARP Snoop is set, ARP Snoop table may be reconfigured by sending the
GARP of proper ip/mac to the port where poisoning is detected.
Command Description
ip arp snoop guard arp- < sec > : Cycle to send GARP
poisoning <sec> <packets> < packets > : Number of GARP Packets
Below-shown is the command to send 5 GARPs in a second. < sec > may be set in the range of 1
~ 10 and < packets >may be set in the range of 5 ~ 60.
ARP Snoop provides with ARP Snoop inspection function to drop Packet when modified ARP
Packet is sent for poisoning attack. Inspection function is available as two types: mac-match and
unsolicited-reply. Mac-match function is the one to drop improper ARP Packet judged when
source mac address of Ethernet header part and source mac address part of ARP packet are not
same. Unsolicited-reply function is the one to judge and drop ARP poisoning attack when multi
ARP reply packets are received in a short time.
Command Description
ip arp snoop inspection <mac- < mac-match > : Source mac address inspection
match/unsolicited-reply> < unsolicited-reply > Reply packet inspection
Both mac-match and unsolicited-reply may be used at the same time and only one mode may
also be used.
localhost(config)#ip arp snoop inspection mac-match
localhost(config)#ip arp snoop inspection unsolicited-reply
To disable the activated ARP Snoop inspection function, execute below-shown command. It is
not impossible to disable one of Mac-match mode or unsolicited-reply mode; if inactivation is
performed when two modes are set, both two are disabled.
localhost(config)#no ip arp snoop inspection
This is the function to drop the ARP packet to which proper IP is not allocated through DHCP
server, by referring the dhcp binding information in arp source address and target address.
Three mode are available and default mode is All: Target, Source, and All.
Command Description
ip arp snoop reply < all, < all > : Both source and target are inspected.
source, target > < source/target > : Either target or source is inspected.
ARP Snoop unicasts reply message to the port received request for the ARP request message
already registered in ARP Snoop table to reduce the quantity of ARP packets.
Command Description
To disable the activated ARP Snoop reply cache function, execute below-shown command.
localhost(config)#no ip arp snoop reply-cache
ARP Snoop may set whether to broadcast or unicast ARP request message.
Four request modes are available: broadcast, protected-broadcast, restricted-broadcast, and
secure-broadcast. Default mode is broadcast. In the broadcast mode, if there is no target
information, ARP request message is transferred to all the server port, transparent port, and
client port in the port types set in DHCP snoop.
Command Description
ip arp snoop request
<broadcast, protected-
ARP Snoop request message setting
broadcast, restrict-broadcast,
secure-broadcast>
When the mode is set as Restrict-broadcast, if the IP information was not properly allocated by
DHCP to source IP, ARP request packet is dropped. At this time, DHCP snoop base-rule should
be set as Deny. ARP request message is transferred to the port to which target belongs to when
there is the information on target; if there is no information on target and the request message is
sent from client port, it is broadcasted to server port and transparent port; if request message is
sent from server port, it is broadcasted to all ports.
The basic action is same in the secure-broadcast mode and restrict-broadcast mode but, if there
is the information on target, the ARP request packet is unicasted to the physical address of
target IP.
In protected-broadcast mode, ARP request packet is broadcasted to server port/router port only.
Therefore, action is possible only when local proxy arp is set in the router and ip dhcp snoop
base-rule deny is set. This setting is performed so that lower layer switch sends all the arp
requests to router to be processed when local-proxy-arp is derived in the router to perform user
isolation.
If arp sticky command is activated, MAC move is not produced in the users or equipments
using static IPs.
Command Description
PPPoE Snooping
This solution is designed for the PPPoE access method and is based on the Access Node
implementing a PPPoE intermediate agent function in order to insert access loop identification.
This functionality is described in the following.
The PPPoE Intermediate Agent intercepts all upstream PPPoE discovery stage packets, i.e. the
PADI, PADR and upstream PADT packets, but does not modify the source or destination MAC
address of these PPPoE discovery packets. Upon reception of a PADI or PADR packet sent by
the PPPoE client, the Intermediate Agent adds a PPPoE TAG to the packet to be sent upstream.
The TAG contains the identification of the access loop on which the PADI or PADR packet was
received in the Access Node where the Intermediate Agent resides. If a PADI or PADR packet
exceeds 1500 octets after adding the TAG containing the access loop identification, the
Intermediate Agent must not send the packet to the Broadband Network Gateway. In response
to the received PADI or PADR packet, the PPPoE Intermediate Agent should issue the
corresponding PADO or PADS response with a Generic-Error TAG to the sender.
The concept of PPPoE Snooping function can know through above figure. Existent PPPoE
Service could not send identification information to PPPoE Server.
PPPoE Snooping function can send message adding Circuit ID or Remote-ID from PPPoE client
to server configured PPPoE or PPPoE+
0x00000DE9 or Corecess ID
PPPoE Snooping function send Corecess ID, Circuit ID and Remote-ID and so on to PPPoE or
PPPoE+ server Using vendor-specfi-tag among one of TLV value
Command Description
configure terminal Enter Global configuration mode.
pppoe-snoop port <Port Type> Sets up whether the port to be determined as .PPPoE snooping is
<Port Number> server/client Server Port or Client Port.
pppoe-snoop port <Port Type>
The PPPoE snoop agent sets up the DSL tag.
<port Number> tag dsl
The following is an example of PPPoE Snooping setup. (During DSL tag setup)
Command Description
Enable the confirmation of Client Session currently at the
Show pppoe-snoop client session
PPPoE Snooping
Command Description
configure terminal Enter Global configuration mode.
The following is an example of setting up compatibility between PPPoE Snooping and Cisco
equipment.
Command Description
configure terminal Enter Global configuration mode..
Command Description
configure terminal Enter Global configuration mode.
pppoe-snoop port <Port Type> Configure ID entering to remote-id of PPPoE Packet to Client
<Port Number> remote-id port to leave equipment.
<WORD> Remote-id is optional
The following is an example of setting up node-id, circuit-id and remote-id with PPPoe
Snooping
This chapter describes how to configure security features on the Corecess S5 System.
Managing Password and Session
Configuring Password
Console is a terminal to connect the system directly through a console port, and virtual terminal
is a terminal to connect the system through Telnet. In the Corecess S5 System, users who access
the system through console or virtual terminal require a password. It can enhance the system
security.
By default, the Corecess S5 System requires a login password. The default login password is
‘corecess’. To change the default login password, use passwd command.
> passwd
Changing password for corecess
(current) UNIX password: ******** Enter the current password.
New UNIX password: ******** Enter the new password.
Retype new UNIX password: ******** Enter the new password again.
passwd: all authentication tokens updated successfully
>
After setting the CLI login password, you should enter the login password at the login prompt
that is shown when you connect the system.
You can set the Privileged mode password that controls access to privilege mode. By default,
the Corecess S5 System does not require the Privileged mode password for entering the
Privileged mode.
You can specify the password for the Privileged mode using enable passwd command. The
following example shows how to set the Privileged mode password to ‘corecess’ by the
enable passwd command.
After setting the Privileged mode password, you should enter the password to go to the
Privileged mode from user mode as follows:
> enable
Password: corecess
Privileged mode is signified by the # prompt. In the Privileged mode, you can enter all
commands to view statistics and configure the system.
Password Encryption
All IDs and passwords on the system can be shown by using the write terminal command.
In the Corecess S5 System, user passwords are stored and displayed by the password
encryption. Even if the writer terminal command is executed, only system administrator can see
the user password.
The following example shows how to add a CLI user who ID and password are ‘guest’ using
the username command and how to display the user using the write terminal command.
# configure terminal
(config)# username guest passwd guest
(config)# end
# write terminal
Building configuration...
Current configuration:
banner incoming "welcome\n"
username recover passwd 8 $1$$nlCC0vP6YG0ZB0Mp685Fy0
username guest passwd 8 $1$$ysap7EeB9ODCrO46Psdbq/
.
.
The default timeout for an unattended telnet session is 10 minutes. To change the login timeout,
enter the following commands:
Command Description
line vty 1. Enter the VTY-line configuration mode.
2. Set the login timeout.
exec-timeout <minute>
<minute>: Timeout in minutes ( 1 ~ 600)
Access list criteria could be the source address of the traffic, the destination address of the traffic,
the upper layer protocol, or other information. Note that sophisticated users can sometimes
successfully evade or fool basic access lists because no authentication is required.
You can use standard access lists to control the Telnet or SNMP access methods to management
functions on the Corecess S5 System.
Internet or LAN
Router 인터넷이나 LAN Server A
Server B
Corecess S5 System
Access List
Source Address : 172.20.128.64
Permit/Deny : Permit
Flow : Out
Host A Host B
IP: 172.20.128.10 IP: 172.20.128.64
In the above example, the access list allows access from the 172.20.128 64 host. Therefore the
host B connected to the Corecess S5 System can access to the Server A or Server B and the host
A can’t access to the Servers.
The Corecess S5 System is basically set to be connected to all networks. Therefore, you should
limit addresses not to access the system using access list for safety if possible.
To define access lists, use the following commands on the Corecess S5 System:
Command Description
configure terminal Enter Global configuration mode.
Permit/Deny packets from the specified source network address.
<list-number> Number of the standard access list (1 ~ 99,
1300 ~ 1999)
permit Permits the frame whose source address matches
access-list <list-number> the condition.
{permit| deny} <source-ip> deny Denies the frame whose source address matches the
/M exact-match condition.
<source-ip>/M The IP address of the source network or
host
exact-match : Exact match of the prefixes
access-list <list-number>
Permit/Deny packets from the specified source host address.
{permit| deny} host
<host-addr> IP Address of the host
<host-addr>
access-list <list-number> Remark: Access list entry comment
remark LINE LINE: Comment up to 100 characters
access-list <list-number>
Permit/Deny packets from all network or host.
{permit| deny} any
end Return to Privileged mode.
show access-list Verify the access list.
Note:
The wildcard is a four-part value in dotted-decimal notation (IP address format) consisting
of ones and zeros. Zeros in the mask mean the packet's source address must match the
<source-ip>. Ones mean any value matches. For example, the <source-ip> and <wild-
card> values 209.157.22.26 0.0.0.255 mean that all hosts in the Class C sub -net
209.157.22.x match the policy.
The packets that do not match any entries in an access list are denied.
The following example shows how to define an access list which permits the access from hosts
in the specified network:
# configure terminal
(config)# access-list 1 permit 192.5.34.0 0.0.0.255
(config)# access-list 1 permit 128.88.0.0 0.0.255.255
(config)# access-list 1 permit 36.0.0.0 0.255.255.255
(config)# end
# show access-list
Standard IP access list 1
permit 192.5.34.0, wildcard bits 0.0.0.255
permit 128.88.0.0, wildcard bits 0.0.255.255
permit 36.0.0.0, wildcard bits 0.255.255.255
The following example shows how to define an access list which denies the access from the
specified host:
# configure terminal
(config)# access-list 2 deny host 171.69.198.102
(config)# access-list 2 permit any
(config)# end
# show access-list
Standard IP access list 2
deny 171.69.198.102
permit any
After you create an access list, you can apply it to terminal line. In this case, access lists can be
applied on both outbound and inbound flows. To restrict terminal line access to the system
using access lists, enter commands such as the following:
Command Description
line vty 1. Enter the VTY-line configuration mode.
2. Apply the access lists to terminal line.
<access-list-number>: Number of an IP access list (1
~ 99, 1300 ~ 1999).
access-class <list-number>
in: Restricts incoming connections between the system
{in | out}
and the addresses in the access list.
out: Restricts outgoing connections between the system and
the addresses in the access list.
The following example shows how to apply the access list to terminal line. The Corecess S5
System allows Telnet access to all IP addresses except the hosts listed in access list 2.
The following example shows how to apply the access list to terminal line. The Corecess S5
System denies connections to networks other than network 192.89.55.0:
# configure terminal
(config)# access-list 12 permit 192.89.55.0 0.0.0.255
(config)# line vty 0 5
(config-line)# access-class 12 out
(config-line)#
After you create an access list, you can apply it to SNMP access. In this case, access lists can be
applied on inbound flow.
To restrict SNMP access to the system using access lists, enter commands such as the following:
Command Description
snmp-server group Apply the access list to SNMP access.
access <list-number> <list-number>: Standard access list number (1 ~ 99, 1300 ~ 1999)
The following example shows how to apply the access list to SNMP access. The Corecess S5
System allows SNMP access to all IP addresses except the hosts listed in access list 2.
Bridge Block
Bridge block prevents LAN interface from a DoS attack. A DoS occurs when ARP or unknown
IP backing the subnet, creating excessive traffic and degrading network performance. Bridge
block uses filtering that measures source mac address activity in a subnet over a measure
interval and compares the measurement with predefined threshold. If the threshold is reached,
further bridge block denies a bridge service of a source mac address, that it cannot accesses in to
the network.
Command Description
Block IP Layer unknown multicast traffic.
bridge block l3-multicast
Bn7000 is not applied as it is L2 device.
bridge block multicast Block unknown multicast traffic.
Block unknown multicast traffic vlan id
bridge block multicast vlan id <1-4094>
<1-4094>.
bridge block unknown-unicast module
Block unknown unicast traffic.
WORD
bridge block mac-flood hold-time
Hold time (sec) for blocking mac.
<1-1024>
bridge block mac-flood port
(fastethernet|gigabitethernet|adsl|giga Enable bridge block mac-flood specific port.
bitethernet |shdsl) WORD
bridge block mac-flood Blocking threshold-arp-packets for threshold
threshold-arp-packets <1-65535> time.
bridge block mac-flood Disable blocking threshold-arp-packets
threshold-arp-packets disable For threshold time.
bridge block mac-flood threshold-
packets Blocking threshold-packets for threshold time.
<1-65535>
bridge block mac-flood threshold-
Disable blocking threshold-packets for
packets
threshold time.
disable
bridge block mac-flood threshold-time
Measure interval threshold time (sec).
<1-360>
Command Description
Restricts incoming and outgoing connections between the Corecess S5 System
access-class
virtual terminal and the addresses in an access list.
access-list Defines a standard IP access list using source addresses for
(Standard) filtering packets received/transmitted through the specific interface.
enable passwd Sets the Privileged mode password.
Sets the interval that the EXEC command interpreter waits until user input is
exec-timeout
detected.
passwd Specifies or changes the CLI login password
snmp-server group Limits hosts which can access to the system through SNMP based on the
access access list.
This chapter describes how to configure the Corecess S5 System for multicast routing protocols.
Multicast Routing Overview
Unicast transmission mode transmits data from one source to one destination. It is used in
general Internet application program such as Telnet or ftp.
Broadcast transmission mode is the transmission of the copy of packet to all receivers in the
same network from one transmitter.
Multicast transmission mode is used in application programs of Internet image conference and
etc, as a mode of more than one transmitters transmitting data to more than one certain
receivers. When a transmitter transmits the pack to a multicast group address, only the
receivers belonging to that multicast group can receive the copy of the packet transmitted by
the transmitter.
The following example shows the difference between unicast transmission mode and multicast
transmission mode.
Video Video
Server Server
Multicast transmission mode minimizes the network resource loss due to repetitive
transmission of the data like the broadcast transmission mode and thus can save network
bandwidth, and can save transmission time since there is no need to transmit the packet to all
receivers separately like the unicast transmission mode.
There is the receiver address displayed on the packet header in unicast transmission, but in the
multicast transmission, marking the multicast group address where receivers belong other than
the receiver address on the header, it transmits the packet.
D class IP address is used for multicast group address. The range of D class is 224.0.0.0 ~
239.255.255.255, and IP address 224.0.0.0 ~ 224.0.0.255 among this range is assigned for other
uses and cannot be used.
Multicast routing is that routers exchange messages for multicast transmission and make
routing trees, then decide the path from source to destination (group members of multicast).
The Corecess S5 System supports the following multicast routing protocols.
IGMP snooping manages multicast traffic at Layer 2 on the Corecess S5 System by allowing
directed switching of IP multicast traffic. Switches can use IGMP snooping to configure Layer 2
interfaces dynamically so that IP multicast traffic is forwarded only to those interfaces
associated with IP multicast devices.
When IGMP snooping is enabled on the Corecess S5 System, the route processor sends out
periodic general queries to all VLANs. The switch processor responds to the route processor’s
queries with only one join request per MAC multicast group. The switch processor creates one
entry per VLAN in the Layer 2 forwarding table for each MAC group from which it receives an
IGMP join request. All hosts interested in this multicast traffic send join requests and are added
to the port mask of this forwarding table entry.
IGMP Proxy
If IGMP(Internet Group Management Protocol) Proxy receives the IGMP join/leave message
from the host, it send the IGMP join/leave message to the router instead of the host.
If it receives the IGMP query from the IGMP router, it transmits the IGMP query to the host
instead of the router.
In other words, it functions as IGMP router for the host and as IGMP host for IGMP router.
DVMRP consists the multicast tree that the root is one source. If the DVMAP source transmits
multicast packets to the DVMRP network, the routers that does not want to receive the packets
of the multicast group transmits the prune message to upstream routers. Then, the routers that
transmit the prune message are removed from the multicast tree, and finally the multicast tree
is completed with the routers who want to receive multicast packets. The prune state is released
after a certain time, and the source transmits the multicast packet to the DVMRP network again.
DVMRP uses RPF (Reverse Path Forwarding) algorithm to maintain a multicast tree that has the
minimum branch. If DVMRP is enabled, the multicast tree is made to transmit multicast packets
to a downstream interface. When the interface receives multicast packets, the interface checks
its DVMRP routing table to find the shortest path. If the interface has the shortest path, the
interface transmits multicast packets to adjacent DVMRP router. If the interface does not have
the shortest path, the interface ignores multicast packets and transmits the prune message to the
upstream router.
After the multicast tree is constructed, pruning of the tree will occur after IP multicast packets
begin to traverse the tree. As multicast packets reach leaf networks (sub-nets with no
downstream interfaces), the local IGMP database checks for the recently arrived IP multicast
packet address. If the local database does not contain the address (the address has not been
learned), the router prunes (removes) the address from the multicast tree and no longer receives
multicasts until the prune age expires.
A DVMRP router restores pruned branches to a multicast tree by sending graft messages
towards the upstream router. Graft messages start at the leaf node and travel up the tree, first
sending the message to its neighbor upstream router. You do not need to perform any
configuration to maintain the multicast delivery tree. The prune and graft messages
automatically maintain the tree.
There are two modes in which PIM operates: Dense and Sparse. The Dense Mode is suitable for
densely populated multicast groups, primarily in the LAN environment. The Sparse Mode is
suitable for sparsely populated multicast groups with the focus on WAN. PIM primarily differs
from DVMRP by using the IP routing table instead of maintaining its own, thereby being
routing protocol independent.
Once PIM is enabled on each router, when a multicast packet is received on a PIM-capable
router interface, the interface checks its IP routing table to determine whether the interface that
received the message provides the shortest path back to the source. If the interface does provide
the shortest path back to the source, the multicast packet is then forwarded to all neighboring
PIM routers. Otherwise, the multicast packet is discarded and a prune message is sent back
upstream.
PIM-SM searches the point where various transmitting places (sources) converges into one
route and set up a tree to where point becomes the route. This type of tree that makes up PIM-
SM is called Shared Tree and the route for Shared Tree is called RP(Rendezvous Point). First,
data are transmitted to RP and then they are transmitted to receivers in each group.
Shared Tree shares one tree per each multicast group. It means that multicast group can use
only one router as RP whereas PIM-SM domain can have multiple RP. At default, Shared Tree
automatically selects RP to be built itself but user customized versions can also be used. User-
defined version of RP is called static RP. Since Shared Tree must pass RP it goes through
different path than optimized SPT (Shortest Path Tree).
BSR is a router that receives candidate RP messages with prioritization information and its own
IP address and transmits information to multicast router for RP selection. When RP is selected
RP router transmits information about its domain to BSR by unicast. Then, BSR include this
message in its Bootstrap message and transmits them to all the PIM-SM routers in its domain.
Based on this information, all the routers can map the multicast group to a RP.
• BSR – The Bootstrap Router (BSR) distributes RP information to the other PIM-SM routers
within the domain. Each PIM-SM domain has one active BSR. For redundancy, you can
configure ports on multiple routers as candidate BSRs. The PIM-SM protocol uses an election
process to select one of the candidate BSRs as the BSR for the domain. The BSR with the
highest BSR priority (a user-configurable parameter) is elected. If the priorities result in a tie,
then the candidate BSR interface with the highest IP address is elected.
• RP – The Rendezvous Point (RP) is the meeting point for PIM-SM sources and receivers. A
PIM-SM domain can have multiple RPs, but each PIM-SM multicast group address can have
only one active RP. PIM-SM routers learn the addresses of RPs and the groups for which they
are responsible from messages that the BSR sends to each of the PIM-SM routers.
Note: We recommends that you configure the same interfaces as candidate BSRs and RPs.
PIM-DM(dense mode) assumes that the downstream networks want to receive the datagram
forwarded to them. The PIM-DM router forwards all packets on all outgoing interfaces until
pruning and truncating occurs. Thus, interfaces with PIM-DM enabled receive the multicast
data stream until it times out. PIM-DM is most useful under these conditions:
In the figure below, the root node (RTA) is forwarding multicast packets for group 229.225.0.1,
which it receives from the server, to its downstream nodes, RTB, RTC, and RTD. Router RTD is
an intermediate router with RTE and RTF as its downstream routers. Because RTE and RTF
have no downstream interfaces, they are leaf nodes. The receivers in this example are those
workstations that are resident on routers RTB, RTC, and RTF.
Server
RTA
229.225.0.1
229.225.0.1
RTB RTC
Group
RTD
Group ....
....
RTE RTF
Group
....
229.225.0.1
As multicast packets reach these leaf routers, the routers check their IGMP databases for the
group. If the group is not in a router’s IGMP database, the router discards the packet and sends
a prune message to the upstream router. The router that discarded the packet also maintains the
prune state for the source, group (S,G) pair. The branch is then pruned (removed) from the
multicast tree. No further multicast packets for that specific (S,G) pair will be received from that
upstream router until the prune state expires. You can configure the PIM Prune Timer (the
length of time that a prune state is considered valid).
For example, in the figure above the sender with address 207.95.5.1 is sending multicast packets
to the group 229.225.0.1. If a PIM router receives any groups other than that group, the router
discards the group and sends a prune message to the upstream PIM router.
Router RTD is a leaf node with no group members in its IGMP database. Therefore, the router
must be pruned from the multicast tree. RTE sends a prune message upstream to its neighbor
router RTD to remove itself from the multicast delivery tree and install a prune state, as seen in
the figure RTE will not receive any further multicast traffic until the prune age interval expires.
When a node on the multicast delivery tree has all of its downstream branches (downstream
interfaces) in the prune state, a prune message is sent upstream. In the case of RTD, if both RTE
and RTF are in a prune state at the same time, RTD becomes a leaf node with no downstream
interfaces and sends a prune message to RTA. With RTD in a prune state, the resulting
multicast delivery tree would consist only of leaf nodes RTB and RTC.
Enabling PIM-SM
To configure PIM-SM network using the Corecess S5 System, enable PIM globally on the switch
and enable PIM-SM locally on VLAN interfaces. To enable PIM-SM, use the following
command in Privileged mode:
Command Description
configure terminal 1. Enter Global configuration mode.
ip multicast-routing 2. Enable PIM on the Corecess S5 System.
3. Enter Interface configuration mode for the VLAN
interface vlan interface that will use PIM-SM.
{id <id> | name <name>} <id> VLAN ID (1 ~ 4094)
<name> VLAN name
4. Configuring IP address of the VLAN interface.
ip address
<ip-address>/<M> <ip-address>: IP address of the VLAN interface
<M>: Subnet mask
ip pim sparse-mode 5. Enable PIM-SM on the VLAN interface.
end 6. Return to Privileged mode.
show running-config 7. Verify the result.
Note: PIM-SM use IGMP to dynamically manage multicast group members. Enabling PIM-
SM on an interface also enables IGMP operation on that interface.
The following example enables PIM-SM on the Corecess S5 System and on the VLAN interface:
# configure terminal
(config)# ip multicast-routing
(config)# interface vlan id 10
(config)# ip address 10.10.10.20/24
(config-if)# ip pim sparse-mode
(config-if)# end
localhost# show running-config
Building configuration...
Current configuration:
!
!
ip multicast-routing
!
interface management
!
interface vlan id 1
!
interface vlan id 10
ip address 10.10.10.20/24
ip pim sparse-mode
!
#
If you enable PIM-SM, PIM-SM will run on the switch with default values for all global and
interface parameters. IGMP is also automatically enabled. Therefore you do not need to
configure all PIM-SM parameters. To change PIM-SM and IGMP parameters according to your
network environment, refer to the following sections:
To configure PIM-SM parameters, see the Configuring PIM and Configuring PIM-SM section
in this chapter.
To configure IGMP parameters, see the Configuring IGMP section in this chapter.
To enable IGMP snooping and configure IGMP snooping parameters, see the Configuring IGMP Snooping
section in this chapter.
Enabling PIM-DM
To configure PIM-DM network using the Corecess S5 System, enable PIM globally on the switch
and enable PIM-DM locally on VLAN interfaces. To enable PIM-DM, use the following
command in Privileged mode:
Command Description
configure terminal 1. Enter Global configuration mode.
Note: PIM-DM use IGMP to dynamically manage multicast group members. Enabling PIM-
DM on an interface also enables IGMP operation on that interface.
The following example enables PIM-DM on the Corecess S5 System and on the VLAN interface:
# configure terminal
(config)# ip multicast-routing
(config)# interface vlan id 10
(config)# ip address 10.10.10.20/24
(config-if)# ip pim dense-mode
(config-if)# end
# show running-config
Building configuration...
Current configuration:
!
!
ip multicast-routing
!
interface management
!
interface vlan id 1
!
interface vlan id 10
ip address 10.10.10.20/24
ip pim dense-mode
!
#
If you enable PIM-DM, PIM-DM will run on the switch with default values for all global and
interface parameters. IGMP is also automatically enabled. Therefore you do not need to
configure all PIM-DM parameters. To change PIM-DM and IGMP parameters according to
your network environment, refer to the following sections:
To configure PIM-DM parameters, see the Configuring PIM and Configuring PIM-DM
section in this chapter.
To configure IGMP parameters, see the Configuring IGMP section in this chapter.
To enable IGMP snooping and configure IGMP snooping parameters, see the Configuring IGMP Snooping
section in this chapter.
Enabling DVMRP
To configure DVMRP network using the Corecess S5 System, enable DVMRP globally on the
switch and locally on VLAN interfaces. To enable DVMRP, use the following command in
Privileged mode:
Command Description
configure terminal 1. Enter Global configuration mode.
Note: DVMRP use IGMP to dynamically manage multicast group members. Enabling
DVMRP on an interface also enables IGMP operation on that interface.
The following example enables DVMRP on the Corecess S5 System and on the VLAN interface:
# configure terminal
(config)# ip multicast-routing
(config)# interface vlan id 10
(config)# ip address 10.10.10.20/24
(config-if)# ip dvmrp
(config-if)# end
localhost# show running-config
Building configuration...
Current configuration:
!
ip multicast-routing
!
interface management
!
interface vlan id 1
!
interface vlan id 10
ip address 10.10.10.20/24
ip dvmrp
#
Note: To disable DVMRP on a VLAN interface, use the ip dvmrp command in Interface
configuration mode and to disable DVMRP on the switch, use the no ip multicast-routing
dvmrp command in Global configuration mode.
If you enable DVMRP, DVMRP will run on the switch with default values for all global and
interface parameters. IGMP is also automatically enabled. Therefore you do not need to
configure all DVMRP parameters. To change DVMRP and IGMP parameters according to your
network environment, refer to the following sections:
To configure DVMRP parameters, see the Configuring DVMRP section in this chapter.
To configure IGMP parameters, see the Configuring IGMP section in this chapter.
To enable IGMP snooping and configure IGMP snooping parameters, see the Configuring IGMP
Snooping section in this chapter.
Enabling IGMP-Proxy
To set the IGMP-proxy network it’s necessary to Enable IGMP-proxy and to set the multicast
group forwarder in the VLAN interface defined in the Corecess S5 system.
To do this, execute the following command in the privileged mode.
Command Description
configure terminal Enter the global configuration mode
ip multicast-routing Enable the multicast routing in the Corecess S5 system
Enter the VLAN interface configuration mode to Enable IGMP-
Proxy
interface vlan
<id> VLAN의 ID (1 ~ 4094)
{id <id> | name <name>}
ID of VLAN
<name> Name of VLAN
Set the IP address of the interface
ip address
<ip-address> IP address to be allocated to the interface
<ip-address>/<M>
<M> the length of subnet mask(the number of bit of the value 1
Enable IGMP-Proxy in the interface
Set the IP IGMP-Proxy in the interface linked to IGMP host
ip igmp-proxy (forwarder)
Set the IP IGMP-Proxy forwarder in the interface linked to
IGMP router.
exit Enter the global configuration mode
Set the multicast group forwarder.
A.B.C.D/M set the address range of multicast group.
ip igmp-proxy forwarder
<id>ID of VLAN(1~4094), VLAN interface to transmit igmp
A.B.C.D/M vlan id <id>
join/leave message of the designated multicast group
(primary | secondary)
(primary | secondary) Use vlan interface as (primary |
secondary) forwarder
end Return the privileged mode
show running-config Verify the configuration
Note: If the IGMP-proxy is intended not to work in the specified interface execute no ip
igmp-proxy in the interface configuration mode.
If the IGMP-proxy protocol is intended not to work in the Corecess S5 system execute no ip
multicast-routing in the global configuration mode.
Refer to the IGMP configuration chapter to set the IGMP function to manage the group members in the
IGMP-Proxy
Refer to IGMP Snooping configuration chapter to Enable and set the IGMP snooping.
In the above figure, MR1-UR1-UR2-MR2 path is used to forward unicast packets and the MR1-
MR2 tunnel is used to forward multicast packets.
You can configure more than one static multicast route. The Corecess S5 System always uses the
most specific route that matches a multicast source address. Thus, if you want to configure a
multicast static route for a specific multicast source and also configure another multicast static
route for all other sources, you can configure two static routes as shown in the examples below.
To add a multicast static route, use the following command in global configuration mode:
Command Description
<source>: IP address of the multicast source
ip pim sparse-
<M>: Mask on the IP address of the multicast source( Bit number that has value
mode mroute
of ‘1’)
<source>/<M>
<rpf-address>: IP address of PIM neighbor. PIM Joins, Grafts, and Prunes are
<rpf-address>
sent to this address.
Note: ip mroute command does not apply to DVMRP route but applies to the multicast
routing protocol that use unicast routing information.
The following example configures the specified sources within the network number 172.16.0.0
are reachable through 172.30.10.13 and all other sources are reachable through 172.30.10.14:
Configuring PIM
This section describes how to configure the following PIM parameters that apply to PIM-SM
and PIM-DM.
The Hello interval specifies how often the local router sends PIM hello messages on this PIM
interface to neighboring routers in the PIM domain. PIM routers periodically send hello
messages so that PIM neighbors can discover each other. Hello messages are multicast using
address 224.0.0.13 (all PIM routers group) and are sent on all communication links.
The default hello interval is 30 seconds and the default hello hold time is 105 (hello interval
times× 3.5). To modifying the hello interval and hold time, use the following commands in
Interface configuration mode:
Command Description
ip pim hello-holdtime <seconds> PIM Hello hold time. Valid range are 1 ~ 65535
<seconds> seconds.
ip pim hello-interval
<seconds> PIM Hello interval. Valid range are 1 ~ 65535 seconds.
<seconds>
The following example shows how to configure PIM hello message interval and hold time for
the VLAN interface:
The Join/Prune interval is the interval at which each PIM interface on the router sends periodic
join/prune messages to its upstream neighbor.
The default Join/Prune message interval is 60 seconds. To change this interval, use the
command in Interface configuration mode.
Command Description
ip pim jp-timer
<seconds>: Join/Prune message interval (1 ~ 65535 seconds)
<seconds>
The following example shows how to set the PIM Join/Prune message interval to 30 seconds for
the VLAN interface:
To prevent the Corecess S5 System from participating in PIM, use the following command in
Interface configuration mode:
Command Description
Note: ip pim neighbor-filter command filters all PIM control messages based on the
given access-list. It can be used to administratively deny a misconfigured PIM neighbor from
participating in PIM. This command does not filter Auto-RP announcements and is only intended
to filter neighbor-to-neighbor packets.
The following example denies PIM packets form the source address 10.0.0.1:
Configuring PIM-SM
You can configure the following PIM-SM features:
• Configuring candidate RP
You can configure the Corecess S5 System as a candidate BSR. To configure the Corecess S5
System as a candidate BSR, use the command in Global configuration mode:
Command Description
<if-name>: Interface name. The IP address of this interface is used as a
candidate BSR. You should specify the name of interface that PIM-SM is
ip pim bsr- enabled.
candidate <if-name> <hash>: Hash Mask Length. This is the number of bits in a group
[<hash>] address that are significant when calculating the group-to-RP mapping.
[<priority>] <priority>: BSR Priority (0-200). When the election process for BSR
takes place, the candidate BSR with the highest priority becomes the
BSR. Default is ‘0’.
Note : The first value to be considered for BSR descision is priority and, if they have same
values, then IP addresses are compared.
To remove the VLAN interface as a candidate BSR, use the no ip pim bsr-candidate
command in Global configuration mode.
Configuring Candidate RP
If you configure PIM-SM, you must also choose one or more routers to be RP (Rendezvous
Point). An RP acts as the meeting place for sources and receivers of multicast data.
To elect an RP, a BSR uses candidate RP messages advertised from candidate RPs. The
candidate RP message has the IP address and priority used for selecting an RP. You can
configure the Corecess S5 System as a candidate RP for the PIM domain. The Corecess S5
System configured as a candidate RP then advertises itself as a candidate RP to the BSR.
To configure the Corecess S5 System as a candidate RP, use the following command in Global
configuration mode:
Command Description
<if-name>: Interface name. The IP address of this interface is used
as a candidate RP. You should specify the name of interface that
ip pim rp-candidate PIM-SM is enabled.
<if-name> [<priority>] <priority>: RP Priority (0-255). When the election process for RP
takes place, the candidate RP with the highest priority becomes the
RP. Default is ‘0’.
The following example configures the VLAN interface as a candidate RP with a priority of 100:
To remove the Corecess S5 System as a candidate RP, use the no ip pim rp-candidate
command in Global configuration mode.
RP for multicast group is required to set up PIM-SM. As explained above, RP can be manually
set by the user and can be set automatically. When selecting RP among the candidate RP no
additional steps are needed for the selection. In automatic option, even if the selected router is
not working properly, the router can automatically be selected. Hence, it is better to have it set
in this way for the selection whenever possible.
In case that RP is not desired to be set automatically, the PR can be set manually. This is called
static RP. Static IP may be convenient in small network but not suitable for large-scaled network.
To set the RP router manually next line should be input in Global Setup Mode.
Command Description
ip pim rp-address
<ip-address> <ip-address> IP address to be used for RP
The following example shows how to set the router interface of which IP address is 30.10.10.1 as
static RP.
(config)# ip pim rp-address 30.10.10.1
(config)#
To delete the static IP use no pim rp-address command in global setup mode as shown
below.
(config)# no ip pim rp-address 30.10.10.1
(config)#
Note : When setting the Static RP all routers in the PIM-SM domain should be set under
same static RP. And it is necessary to check if the selected router is in the backbone and
connected with other parts of the network
You can prevent unauthorized sources from registering with the RP. If an unauthorized source
sends a register message to the RP, the RP will immediately send back a register-stop message.
To configure a candidate RP router to filter PIM register messages, use the following command
in Global configuration mode:
Command Description
The following example shows how to restrict the RP from allowing sources in the specified
access list range of addresses to with the specified access list address range to register with the
RP:
You can take a defensive measure to prevent a misconfigured leaf router from interrupting PIM
service to the remainder of a network. To do so, configure the local router to accept Join/Prune
messages only when the group is in the group range specified by the access list.
To configure this feature, use the following command in Global configuration mode:
Command Description
Interface for Candidate RP among interfaces that are set
up for <if-name> Corecess S5 system, with enabled PIM-SM,
ip pim accept-rp list
must be used.
<access-list-number>
<access-list-number>: The standard access-list number (1 ~
99, 1300 ~ 1999)
ip pim rp-address <ip-address> Specific RP Address
<ip-address> <access-list-number> Access List Number (1 ~ 99,
<access-list-number> 1300 ~ 1999
The following example shows how to configure the router to accept Join/Prune messages only
when the multicast group is 224.2.2.2 about static RP 10.1.1.1:
You should specify the IP source address of register message only when the IP source address
of a register message is not a uniquely routed address to which the RP can send packets. This
situation may occur if the source address is filtered such that packets sent to it will not be
forwarded or if the source address is not unique to the network. In these cases, the replies sent
from the RP to the source address will fail to reach the DR, resulting in PIM-SM protocol
failures.
To configure the IP source address of a register message to an interface address other than the
outgoing interface address of the DR leading toward RP, use the following command in Global
configuration mode:
Command Description
The following example shows how to configure the IP source address of the register message to
the loopback 3 interface of a DR:
The Corecess S5 System can limit the number of register messages that the DR will allow for
each (S, G) entry.
To set a limit on the maximum number of PIM-SM register messages sent per second for each (S,
G) routing entry, use the following command in Global configuration mode:
Command Description
ip pim register- <rate>: Maximum number of register messages sent per second by the
rate limit <rate> router. Valid range are 1 ~ 65535.
The following example shows how to configure the maximum number of PIM-SM register
messages sent per second to 2:
The RP sends a register-stop message when it receives native multicast packets from the DR and
there are no downstream routers (receivers) to forward these packets to. The source’s DR stops
the outgoing interface from sending further register packets and sets its register suppression
timer. The register suppression timer determines how long the DR waits before sending register
messages back to the RP.
The default register suppression timer is 60 seconds. To set the register suppression timer, use
the following command in Global configuration mode:
Command Description
ip pim register- <seconds> Register suppression timer. Valid range are 1 ~ 65535
suppression <seconds> seconds.
The following example sets the register suppression timer to 120 seconds:
RP reachability messages are generated by RPs periodically and distributed down the (*, G) tree
established for the group. This allows downstream routers to detect when their current RP has
become unreachable and triggers joining toward an alternate RP.
By default, the Corecess S5 System is set to not generate RP reachability message. To generate
and distribute a periodic RP reachability message, enter the ip pim register-rp-
reachability command in Global configuration mode:
In a typical PIM-SM domain, there may be two or more paths from a DR for a multicast source
to a PIM group receiver. One is path through the RP and the other is Shortest Path (STP).
By default, the Corecess S5 System switches from the RP to the SPT when a source sends at a
rate greater than or equal to 1000bps rate. To configure the Corecess S5 System to send
multicast packets using the RP indefinitely and does not switch over to the SPT, use the ip pim
spt-threshold infinity command in Global configuration mode.
# configure terminal
(config)# ip pim spt-threshold infinity
To configure the Corecess S5 System to send multicast packets using the STP when a source
sends at a rate greater than or equal to 1000bps rate, use the no ip pim spt-threshold
infinity command in Global configuration mode:
If you configure an interface to be the PIM domain border, no PIM Version 2 BSR messages will
be sent or received through the interface. Configure an interface bordering another PIM domain
to avoid BSR messages from being exchanged between the two domains. BSR messages should
not be exchanged between different domains, because routers in one domain may elect RPs in
the other domain, resulting in protocol malfunction or loss of isolation between the domains.
To prevent BSR messages from being sent or received through an interface, enter the ip pim
bsr-border command in Interface configuration mode.
The following example configures the VLAN interface to be the PIM domain border:
Note: ip pim bsr-border command does not set up multicast boundaries. It sets up
only a PIM domain BSR message border.
The DR priority indicates the priority level for a DR on the LAN. The higher the number, the
higher the priority. A PIM-SM router configured with a DR election priority sends to its PIM
neighbors a Hello message that contains its priority level. The PIM-SM router with the highest
priority level is elected the DR for the LAN. Local routers not configured with a DR election
priority level elect a DR based on the highest IP address.
The default DR priority is 1. To specify the DR priority, use the following command in Interface
configuration mode:
Command Description
ip pim dr-priority
<priority> <seconds>: DR priority. Valid range are 0 ~ 4294967294.
The following example shows how to set the DR priority for the VLAN interface to 200:
By default, the Corecess S5 System is compatible with the standard PIM-SM specification
defined in RFC 2362. However, you can enable the Corecess S5 System to interoperate with
routers configured with nonstandard PIM implementations that do not comply with RFC 2362.
To enable router compatibility with RFC 2362, use the following commands:
Command Description
configure terminal 1. Enter Global configuration mode.
2. Enable the PIM-SM router to computes checksum on the PIM header
and data portion of the register packet.
ip pim cisco-register-
group-list: Specifies the number of a standard access list that
checksum [group-list
describes the multicast groups.
<access-list-number>]
<access-list-number>: Access list number (1 ~ 99,
1300 ~ 1999)
3. Enable the PIM-SM router to send non-zero prefix count in RP
ip pim crp-cisco-prefix
advertisement messages.
ip pim ignore-rp-set- 4. Enable the PIM-SM router to use the hash mask length instead of
priority priority to elect RP.
5. Enter Interface configuration mode for the VLAN interface to
interface vlan configure.
{id <id> | name <name>} <id>: VLAN ID (1 ~ 4094)
<name>: VLAN name
6. Prevent the PIM-SM router from appending generation identifiers to
ip pim exclude-genid
Hello messages that it sends to its neighbors.
The following example shows how to enable router compatibility with RFC 2362:
Note: Use the ip pim-sm cisco-rp-prefix-count command only when the Cisco
router that does not support RFC 2362 is elected as the BSR.
Corecess S5 system supports distribution of multicast traffic load via ECMP (Equal-Cost-Multi-
Path) routing path. To use distribution of multicast traffic load PIM-SM must be enabled for the
interface in which ECMP routing path exists.
Distribution of multicast traffic load is done in the following process. At the router that
performs PIM Join, for (*, G) Join, each group, using different routing path, transmits by
applying hash function of which the keys are used as group address, to ECMO routing path.
For (S, G) Join, similar ways are used and it transmits Join to the traffic sources through
different routing paths
To apply distribution of multicast traffic load, following commands should be used. In this
example, basic PIM-SM setup is assumed.
Command Description
The following is example of setting distribution of multicast traffic load in Corecess S5 system.
Note : In the hash distribution of multicast traffic load, the traffic may be distributed exactly
into 1/n over ECMP paths.
Configuring PIM-DM
This section describes how to configure the PIM-DM state refresh control message interval.
PIM-DM builds source-based multicast distribution trees that operate on a flood and prune
principle. Multicast packets from a source are flooded to all areas of a PIM-DM network. PIM
routers that receive multicast packets and have no directly connected multicast group members
or PIM neighbors send a prune message back up the source-based distribution tree toward the
source of the packets. As a result, subsequent multicast packets are not flooded to prune
branches of the distribution tree. However, the pruned state in PIM-DM times out
approximately every 3 minutes and the entire PIM-DM network is reflooded with multicast
packets and prune messages. This reflooding of unwanted traffic throughout the PIM-DM
network consumes network bandwidth.
The PIM-DM State Refresh feature keeps the pruned state in PIM-DM from timing out, which
saves network bandwidth by greatly reducing the reflooding of unwanted multicast traffic to
pruned branches of the PIM-DM network. This feature also enables PIM-DM routers to
recognize topology changes (sources joining or leaving a multicast group) before the state
refresh timeout period.
If you enable PIM-DM on the Corecess S5 System, the state refresh feature is automatically
enabled. To disable the state refresh feature, use the ip pim state-refresh disable
command.
To configure the origination interval for the state refresh control message, use the following
command:
Command Description
Note: The origination interval for the state refresh control message must be the same for all
PIM routers on the same LAN. Specifically, the same origination interval must be configured
on each router interface that is directly connected to the LAN
The following example shows how to configure the origination interval for the state refresh
control message to 60 seconds.
Configuring DVMRP
This section describes how to configure a metric for DVMRP interface.
The DVMRP router uses the metric when establishing reverse paths to some networks on
directly attached interfaces.
The default DVMRP metric is 1. To modify a DVMRP interface’s metric, use the following
command in Interface configuration mode:
Command Description
ip dvmrp metric
<metric> <ip-address>: The metric for this interface. Valid range are 1 ~ 32.
The following example shows how to set a metric of 5 for the VLAN interface:
Configuring IGMP-Proxy
Corecess S5 system is already set to be performed without additional configuration on IGMP-
Proxy. If necessary, it’s possible to set the following IGMP-Proxy configuration
Command Description
The following is the example to set the bootstrap of VLAN interface having ID 2.
To set the unsolicited-report, execute the following command in the interface configuration
mode
Command Description
ip igmp-proxy
<seconds> a period of transmitting the IGMP join. Default value is 125
unsolicited-reopr
sec
(<seconds>)
The following is the example to set the unsolicited-repot of VLAN interface whose ID is 2
(config)# interface vlan id 2
(config-if)# ip igmp-proxy unsolicited-reoprt
(config-if)#
Command Description
ip igmp-proxy fwd-vif-
<seconds> Time to fix the multicast group. Default value is 255 sec
sticky (<seconds>)
The following is the example to set the unsolicited-repot of VLAN interface whose ID is 2.
(config)# ip igmp-proxy fwd-vif-sticky
For forwarder load distribution, multi forwarder interfaces are distributed into primary mode
or secondary mode. To set the multi forwarder interfaces execute the following command in the
global configuration mode.
Command Description
Set the multicast group address range of A.B.C.D/M
ip igmp-proxy
forward A.B.C.D/M <id> ID of VLAN(1~4094) VLAN interface to transmit IGMP join/leave
vlan id <id> of the designated multicast group.
(primary |
secondary) (primary | secondary)Use the VLAN interface as (primary | secondary)
forwarder
The following is the example to set the IGMP-Proxy interface redundancy configuring VLAN
interfaces having ID(2, 3) as primary/secondary forwarder.
The following is the example to set the IGMP-Proxy interface load distribution configuring
VLAN interfaces having ID(2, 3) as primary/secondary forwarder
(config)# ip igmp-proxy forward 224.0.0.0/4 vlan id 2 primary
(config)# ip igmp-proxy forward 224.0.0.0/4 vlan id 3 primary
Command Description
Set the multicast group address range of A.B.C.D/M
ip igmp-proxy
forward A.B.C.D/M <id> ID of VLAN(1~4094) VLAN interface to transmit IGMP join/leave
vlan id <id> of the designated multicast group.
(primary |
secondary) (primary | secondary)Use the VLAN interface as (primary | secondary)
forwarder
The following is the example to set that the multicast group of 233.18.1.0/24 receives multicast
packet for VLAN interface having ID 2 and the multicast group of 233.18.2.0/24 receives
multicast packet for VLAN interface having ID 3
The following is the example to set that the multicast group of 233.18.1.0/24 receives multicast
packet for VLAN interface having ID 3 and the other multicast group receives multicast
packet for VLAN interface having ID 2
Configuring IGMP
You can use the Corecess S5 System without additional configuration of the IGMP. If necessary,
you may configure the following IGMP features.
To control the multicast groups that hosts on the subnet serviced by a VLAN interface can join,
use the following command in Interface configuration mode:
Command Description
ip igmp access-group
<access-list-number> <seconds> Number of a standard IP access list (1 ~ 99)
In the following example, hosts serviced by the VLAN interface can join the group 225.2.2.2
only:
By default, IGMP querier is selected by the automatic IGMP querier selection mechanism.
However, you can configure the specified interface to act as IGMP querier using ip igmp
querier command in interface configuration mode.
To configure IGMP static querier on a VLAN interface, use the ip igmp querier command in
Interface configuration mode.
The following example enables IGMP static querier on the VLAN whose id is ‘1’:
Note: Enabling IGMP static querier may severly affect multicast forwarding. We recommend
using automatic IGMP querier selection mechanism.
To disable IGMP static querier on a VLAN interface, use no ip igmp querier command in
the interface configuration mode.
You can configure statistically the router based on priority using ip igmp non-querier and
ip igmp querier IGMP commands. Any router port can be statically configured as IGMP
querier or non-querier without changing the IP address of the router port.
Multicast routers send IGMP host-query messages to discover which multicast groups are
present on attached networks. These messages are sent to the all-systems group address of
224.0.0.1 with a TTL of 1. The IGMP query interval period defines how often a router will query
an interface for group membership. Possible values are 10 ~ 43200 seconds and the default
value is 125 seconds.
To modify the IGMP query interval, use the following command in Interface configuration
mode:
Command Description
<seconds>: Frequency, in seconds, at which to send IGMP host-
ip igmp query-interval
query messages (10 ~ 43200, seconds). Default setting is 125
<seconds>
seconds.
The following example changes the frequency at which the designated router sends IGMP host-
query messages to 120 seconds:
To restore the default IGMP query interval, use the no igmp query-interval command in
interface configuration mode.
Note: IGMP intervals come with preset values. The defaults work well in most network s, we
recommend that you use the default interval value.
You can specify the period of time before the Corecess S5 System takes over as the querier for
the interface, after the previous querier has stopped doing so. By default, the router waits twice
the query interval specified by the ip igmp query-interval command. After that time, if
the Corecess S5 System has received no queries, it becomes the querier.
By default, the IGMP query timeout value is set to 255 seconds. To change the IGMP query
timeout, use the following command in Global configuration mode:
Command Description
<seconds>: Number of seconds that the router waits after the
ip igmp querier-timeout
previous querier has stopped querying and before it takes over as
<seconds>
the querier. Valid range are 30 ~ 1200 seconds.
The following example changes the IGMP query timeout value to 300 seconds:
To reset the IGMP query timeout value, use the no ip igmp query-timeout command.
By default, the maximum query response time advertised in IGMP queries is 10 seconds. If the
router is using IGMP Version 2, you can change this value. The maximum query response time
allows a router to quickly detect that there are no more directly connected group members on a
LAN.
To change the maximum query response time, use the following command in Interface
configuration mode:
Command Description
ip igmp
query-max-response-time <seconds>: The maximum query response time advertised in
<seconds> IGMP queries. Valid range are 1 ~ 20 seconds.
The following example changes the maximum query response time value to 15 seconds:
To restore the default value, use the no ip igmp query-max-response time command.
Normally a router sends an IGMP group-specific query message upon receipt of an IGMPv2
group leave message. The router will stop forwarding traffic for that group only if no host
replies to the query within the timeout period. The timeout period is determined by the ip
igmp last-member-query-interval command and the IGMP robustness variable, which
is defined by the IGMP specification.
If IGMP immediate leave feature is enabled, the router assumes that only one host has joined
the group and stops forwarding the group's traffic immediately upon receipt of an IGMPv2
group leave message.
By default, IGMP immediate leave feature is disabled. To minimize the leave latency of IGMP
memberships and only one receiver host is connected to each interface, use the following
command in Interface configuration mode:
Command Description
ip igmp immediate-leave
group-list <access-list-number>: Access list number (1 ~ 99, 1300 ~
<access-list-number> 1999)
The following example shows how to enable the immediate leave feature on the VLAN
interfaces for the multicast groups 255.2.2.2:
When a router receives an IGMP Version 2 leave group message on an interface, it waits twice
the query interval; after which, if no receiver has responded, the router drops the group
membership on that interface.
By default, the Corecess S5 System sends the Group-Specific Queries message twice every 1000
milliseconds to the group being left.
To configure the count to which the router sends IGMP group-specific host query messages and
the frequency at which the router sends IGMP group-specific host query messages, use the
following commands in Interface configuration mode:
Command Description
ip igmp last-member-query- <count>: The count to which the router sends IGMP group-
count <count> specific host query messages.
ip igmp last-member-query- <interval>: The frequency at which the router sends IGMP
interval <interval> group-specific host query messages.
Specifies in tenths of a second how long the system waits after receiving an IGMP leave
message before it sends another query.
The following example shows how to modify the last member query count and interval for the
VLAN interface:
By default, IGMP snooping is globally disabled on the Corecess S5 System. When globally
enabled or disabled, it is also enabled or disabled in all existing VLAN interfaces. IGMP
snooping is by default disabled on all VLANs, but can be enabled and disabled on a per-VLAN
basis. Global IGMP snooping override the VLAN IGMP snooping. If global snooping is
disabled, you cannot enable VLAN snooping. If global snooping is enabled, you can enable or
disable VLAN snooping.
To globally enable IGMP snooping on the Corecess S5 System and enable VLAN IGMP
snooping, use the following command in Global configuration mode:
Command Description
ip igmp snoop
<vlan-id>: ID of a VLAN to enable IGMP snooping.
[vlan id <vlan-id>]
First, execute ip igmp snoop command to enable igmp snooping so that igmp snooping is
applied on vlan interface. After the execution of ip igmp snoop, enable igmp snooping for each
of vlan interface.
If ip igmp snoop is not executed you cannot enable igmp snooping on vlan interface.
The following is example of enabling igmp snooping on vlan id for 2 person interface.
(config)# ip igmp snoop
(config)# ip igmp snoop vlan id 2
Execute no ip igmp snoop vlan id number to disable igmp snoop on the interface where igmp
snooping is enabled.
If you do not want to use igmp snooping on the equipment regardless of vlan interface, execute
no ip igmp snoop command. Then igmp snooping is disabled for all vlan interfaces.
(config)# no ip igmp snoop
(config)# no ip igmp snoop vlan id 2
However, if a multicast router receives a membership query message from the Corecess S5
System, which is not a multicast route, but a system that provides IGMP snooping functions,
and recognizes it as a multicast router, it may stop its role as the IGMP querier (if the IP address
of the Corecess S5 System is smaller than the IP address of the multicast router). If this happens,
a problem may occur in which the multicast router stops forwarding multicast traffic from
outside the network into the LAN. Therefore, membership query messages must not be sent
from the Corecess S5 System to the multicast router. In order to do so, the port connected to the
multicast router must be manually set as a router port.
To configure a static router port, use the command in the Global configuration mode:
Command Description
The following example adds the Gigabit Ethernet port 17/1 as a router port:
To remove a multicast router, use the no ip igmp snooping mrouter command in Global
configuration mode.
Note: Multicast routers that support only IGMPv1 cannot process host membership report
messages received from devices that support IGMPv2. In addition, multicast routers which
support only IGMPv1 can not understand Leave messages, which are sent by hosts leaving
multicast groups. Since there is no way for IGMP snooping devices, such as the Corecess
S5 System, to automatically recognize ports connected to these IGMPv1 multicast r outers,
the user must manually specify them.
When you enable IGMP immediately leave feature, the Corecess S5 System immediately
removes a port when it detects an IGMP version 2 leave messages on that port.
To enable IGMP immediately leave feature on a port interface, use the following command in
Global configuration mode:
Command Description
This example shows how to enable IGMP fast-leave processing on the Gigabit Ethernet port 17/1:
Hosts normally join multicast groups dynamically, but you can also configure a host statically
on an interface.
To add a port as a member of a multicast group, use the following command in Global
configuration mode:
Command Description
ip igmp snoop static-mgroup
<group-address> IP address of multicast group
<group-address> port
<slot>/<port> Slot number and port number
gigabitethernet <slot>/<port> [vlan
id <vlan-id>] <vlan-id> VLAN ID (1 ~ 4094)
This example shows how to add the Gigabit Ethernet port 17/1 as a member of the group
01:00:5e:00:02:03:
To remove the port from the multicast group, use the no ip igmp snooping static-
mgroup command.
IGMP group membership time defines how long a group will remain active on an interface in
the absence of a group report. You can specify how many seconds an IP Multicast group can
remain on a Corecess S5 System interface in the absence of a group report.
To change IGMP group membership time, use the following command in Global configuration
mode:
Command Description
ip igmp snoop membership <seconds> The IGMP group membership time in seconds
timeout <seconds> from 1 to 1200 seconds.
By default, each port of the Corecess S5 System can belong to up to 1024 multicast groups. To
configure the maximum number of multicast groups that a port can belong to, use the following
command in Global configuration mode:
Command Description
The following example shows how to specify the number of multicast groups for the Gigabit
Ethernet port 17/1 to 2048:
Command Description
The following example shows how to display the IP multicast routing table written down to the
device for all groups.
# show ip mroute
To see information other than the information on the multicast routing table that was
maintained by multicast routing protocol device, and to see the information on multicast
routing table of Corecess S5, execute show ip mroute <protocol> command in the privilege
mode.
Command Description
The following example shows how to display the IP multicast routing table which is maintained
by the multicast protocols for all groups.
The following table describes the fields in the show ip mroute <protocol>command output:
Field Description
Information about the entry:
- D Entry is operating in PIM-DM
- S Entry is operating in PIM-SM
- V Entry is operating in DVMRP
- C A member of the multicast group is present on the directly connected
interface
- L The router itself is a member of the multicast group
Flags: - P Route has been pruned
- G Route has been graft
- R Indicates that the (S,G) entry is pointing towards the RP.
- T Indicates that packets have been received on the shortest path source tree.
- F Indicates that the software is Registering for a multicast source
- J For (*, G) entries, indicates that the rate of traffic flowing down the shared
tree is exceeding the SPT-Threshold set for the group. For (S, G) entries,
indicates that the entry was created because the SPT-Threshold for the group
was exceeded.
How long in hours, minutes, and seconds the entry has been in the IP multicast
Timers::
routing table / How long in hours, minutes, and seconds until the entry will be
Uptime/Expires
removed from the IP multicast routing table on the outgoing interface
IP multicast routing table. The entry consists of the IP address of the source
(10.0.0.1, 224.1.1.1)
router followed by IP address of the multicast group.
Expected interface for a multicast packet from the source. If the packet is not
Incoming interface:
received on this interface, it is discarded.
PIM-SM RP information
To display basic configuration information for PIM, use the show ip pim configuration
command in Privileged mode.
The following example shows how to display basic configuration information for PIM on the
Corecess S5 System:
The following table describes the fields in the show ip pim configuration command output:
Field Description
PIM Daemon Start Time How many seconds have passed since the router is started
PIM Daemon Up Time How many seconds have passed since the PIM is enabled
The interval at which each PIM interface on the router sends periodic
PIM Default Hello Interval
hello messages to its PIM neighbor
How many seconds the local router will wait for a hello message from
PIM Default Hello Holdtime a neighbor before determining that the neighbor is no longer present
and removing cached PIM forwarding entries for the neighbor.
The interval at which the local router sends PIM-SM Join/Prune
PIM Join/Prune Interval
messages for the multicast groups it is forwarding.
The amount of time a receiver must keep the Join/Prune state alive,
PIM Join/Prune Holdtime
in seconds.
The interval at which the BSR sends the RP set to the RPs within the
PIM-SM Bootstrap Interval
PIM-SM domain.
To display information about interfaces configured for PIM, use the show ip pim
interface [detail] command in Privileged mode.
The following is sample output from the show ip pim interface command:
The following table describes the fields in the show ip pim interface command output:
Field Description
The following is sample output from the show ip pim interface detail command:
The following table describes the fields in the show ip pim interface detail command
output:
Field Description
vlan10 (vif 0) Name of the VLAN interface (Index)
Address IP address of the VLAN interface
DR IP address of the DR
Hello period Interval for the origination of the PIM hello messages
Indicates how many seconds will pass before the local router sends its next
Next Hello
hello message.
Indicates whether the interface is enabled as a PIM domain border (enable,
PIM domain border
disable)
Neighbors IP address of the PIM neighbor
To display information about neighbor configured for PIM, use the show ip pim neighbor
[detail] command in Privileged mode.
The following is sample output from the show ip pim neighbor command:
The following table describes the fields in the show ip pim neighbor command output:
Field Description
Neighbor Address Address of Neighbor
Interface Interface connected to Neighbor
Uptime Time that discovers Neighbor
Expires Time that lease connection when the Neighbor does not response
Version PIM version of Neighbor
DR Priority DR priority of Neighbor
Mode PIM mode of Neighbor
To display the PIM-SM bootstrap router (BSR) information, use the show ip pim bsr-
router command in Privileged mode.
The following table describes the fields in the show ip pim bsr-router command output:
Field Description
Uptime Length of time that this router has been up (in hours, minutes, and seconds
Next Time (in hours, minutes, and seconds) in which the next candidate RP
Cand_RP_advertisement advertisement will be sent
To display all group-to-RP mappings of which the router is aware, use the show ip pim rp
mapping command in Privileged mode.
The following is sample output from the show ip pim rp mapping command:
# show ip pim rp mapping
PIM Group-to-RP Mappings
This system is the Bootstrap Router (v2)
Group(s): 224.0.0.0/4
RP: 2.2.2.2
Info source: 2.2.2.2, via bootstrap, priority 192
Uptime: 00:02:23, expires: 00:02:10
Dynamic mapping : 1
Static mapping : 0
Total mapping : 1
#
The following table describes the fields in the show ip pim rp mapping command output:
Field Description
Address of the multicast group about which to display RP information (Static,
Group(s)
Dynamic)
RP Address of the RP for that group.
Info source PIM that transmits RP information
Length of time the RP has been up (in days and hours). If less than 1 day, time is
Uptime
shown in hours, minutes, and seconds.
To display which rendezvous point (RP) is being selected for a specified group, use the show
ip pim rp-hash <group-address> command in Privileged mode.
The following is sample output from the show ip pim rp-hash command with the group
address 224.0.0.0 specified.
To display DVMRP information for the Corecess S5 System, use the show ip pim
configuration command in Privileged mode.
The following is sample output from the show ip pim configuration command:
The following table describes the fields in the show ip dvmrp configuration
command output:
Filed Description
DVMRP Daemon Start Time How many seconds have passed since the router is started
DVMRP Daemon Up Time How many seconds have passed since the PIM is enabled
DVMRP Default Metric The metric (or cost) of all DVMRP interfaces on the router.
(Continued)
Filed Description
DVMRP Probe Interval The interval between the transmissions of probe messages.
DVMRP Neighbor Timeout If no message is received from a DVMRP neighbor during this time
Interval period, the neighbor is considered “down.”
The interval between the transmissions of route reports. A route
DVMRP Route Report Interval
report advertises all active routes.
DVMRP Route Expiration Time A route expires if it has not been refreshed within this time period.
DVMRP Route Discard Time The period of time before a route is deleted on a DVMRP router.
The period during which a deleted route is advertised with a metric
DVMRP Holddown Period
of infinity.
To display the status of a VLAN interface running DVMRP, use the show ip dvmrp
interface command in Privileged mode.
The following table describes the fields in the show ip dvmrp interface command output:
Filed Description
To display information about DVMRP neighbors, use the show ip dvmrp neighbor
command in Privileged mode.
The following table describes the fields in the show ip dvmrp neighbor command output:
Filed Description
IP address of the DVMRP neighbor from which the interface has received Probe
Neighbor Address
messages.
Interface DVMRP interface for which neighbor information is displayed.
The amount of time the neighbor has been “up.” /
Uptime/Expires
The amount of time before the neighbor expires
State The status information of the DVMRP neighbor
Version of DVMRP that is operating on the VLAN interface. 3 indicate compliance
Ver
with the draft-ietf-idmr-dvmrp-v3-10 draft.
To display information about DVMRP routes, use the show ip dvmrp route command in
Privileged mode.
The following table describes the fields in the show ip dvmrp route command output:
Filed Description
To display the prunes that were received, use the show ip dvmrp prune command in
Privileged mode.
The following table describes the fields in the show ip dvmrp prune command output:
Field Description
Prune Snd Interface The interface that the local router sends the Prune message.
Prune Rcv If Counts The number of interface that receives Prune messages
Prune Exptime The amount of time before the prune message expires
If the command show ip igmp-proxy forward [A.B.C.D] is executed in the privileged mode,
you can find out the multicast group forwarder information.
The following is the example to execute the command show ip igmp-proxy forward in the
Corecess S5 system.
The following shows the meaning of each item output in case of executing the command show
ip igmp-proxy forwarder
Field Description
forwarder: vlan2
The state of the VLAN2 interfaces configured as a forwarder.
primary up
The following is the example to execute the command show ip igmp-proxy interface
in the Corecess S5 system
The following shows the meaning of each item output in case of executing the command ip
igmp-proxy interface.
Field Description
The following shows the meaning of each item output in case of executing the command show
ip igmp-proxy local-members
Field Description
vlan1 A name of a VLAN interface
(*, 233.18.254.1) Multicast packet transmitter, Multicast group address
INCLUDE The state of multicast group transmission (INCLUDE, EXCLUDE)
(*, 233.18.254.1)
upstream vlan2 state: JOINED mode: INCLUDE
Outgoing interface list:
vlan1 (10.10.10.10), Forward/INCLUDE, 00:00:22/00:00:00
The following shows the meaning of each item output in case of executing the command show
ip igmp-proxy mroute.
Field Description
(*,G) Entries (*,G) The number of the Entries
(S,G) Entries (S,G) The number of the Entries
Upstream vlan2 state: The state of multicast group routing (JOINED, PRUNED)
JOIND mode: INCLUDE The mode of multicast group routing (INCLUDE, EXCLUDE)
vlan1 (192.168.1.254),
multicast group forwarding interface information
Forward/INCLUDE
#
The following shows the meaning of each item output in case of executing the command show
ip igmp-proxy reception-state
Field Description
vlan2 The name of VLAN interface
(*, 233.18.254.1) (Multi-cast packet departure, Multicast group address)
INCLUDE The reception state of multi-cast group(INCLUDE, EXCLUDE)
To display IGMP information for interfaces configured on the Corecess S5 System, enter the
show ip igmp interface command in Privileged mode.
The following is sample output from the show ip igmp interface command:
The following table describes the fields in the show ip igmp configuration command output:
Field Description
Interface Name of the interface
Internet address IP address of the interface
IGMP querier Indicates whether the interface is IGMP querier or not.
IGMP query interval The time interval between general queries.
The timeout time before the system takes over as the querier for the
IGMP querier timeout
interface.
IGMP max query The maximum amount of time within which a host must send a membership
response time report after it receives a query.
Last member query
The number of seconds between group-specific queries.
response interval
Last member query
The number of group-specific queries that will be sent.
count
IGMP querying router IP address of the IGMP querier
IGMP is Indicates whether IGMP is enabled or not on the interface.
To display the multicast groups that are directly connected to the Corecess S5 System and that
were learned via IGMP snooping, use the show ip igmp snooping command in Privileged
mode.
Command Description
<address>: Address of the multicast group for which to display
show ip igmp group host memberships.
[<address> | <if-name>] <if-name>: Name of the interface for which to display host
memberships.
The following example displays the multicast groups that are directly connected to the Corecess
S5 System:
The following example shows how to display the information about the multicast group
224.3.3.2 by using the show ip igmp group <address> command:
The following example shows how to display the information about the multicast groups on the
default VLAN interface by using the show ip igmp group <if-name> command:
The following table describes the fields in the show ip igmp group command output:
Field Description
Group Address The IP address of the multicast group.
Interface Name of the interface that belongs to the multicast group.
Uptime The amount of time that the interface has been a member of the group.
Expires The amount of time left before membership to the group expires.
Last Reporter The interface on which a membership report for the group was last received.
To display IGMP snooping, use the show ip igmp snoop command in Privileged mode.
Command Description
<vlan-id> VLAN ID (1 ~ 4094). Displaying IGMP snooping
show ip igmp snoop information for a specific VLAN interface.
[vlan id <vlan-id> |
static Displays static multicast groups.
static | dynamic]
dynamic Displays dynamic multicast groups.
The following example displays the IGMP snooping information on the Corecess S5 System.
The following example displays the IGMP snooping of the default VLAN using the show ip
igmp snoop vlan command.
The following example displays the multicast groups that were learned via IGMP snooping:
The following table describes the fields in the show ip igmp snooping command output:
Filed Description
group ip IP Address of the multicast group. In case of a static multicast group, 0.0.0.0 is displayed.
How long in seconds until the entry is removed from the IGMP groups table. In case of a
timeout left
static multicast group, 0 is displayed.
The following example shows how to display information on multicast router interfaces on the
Corecess S5 System:
The following table describes the fields in the show ip igmp snoop mrouter command
output:
Filed Description
port Slot number and port number of the multicast router port
vlan ID of the VLAN that the multicast router port belongs to.
router ip IP address of multicast router that the multicast port is connected to.
Total Number The number of multicast router ports that are registered to the system.
To display the list of the VLANs and ports which IGMP immediately leave feature is enabled on,
use the show ip igmp snoop fast-leave command in Privileged mode. If you enable
IGMP immediately leave feature, the system immediately removes a port when it detects an
IGMP version 2 leave messages on that VLAN or port.
The following is the sample output from show ip igmp snoop fast-leave command:
To display IGMP group membership time which defines how long a group will remain active
on an interface in the absence of a group report, use the show ip igmp snooping
membership timeout command in Privileged mode.
The following table lists the commands for configuring IP multicast on the Corecess S5 System
and displaying IP multicast configuration:
Command Description
Enables DVMRP (Distance Vector Multicast Routing Protocol) on a VLAN
ip dvmrp
interface.
ip dvmrp metric Configures the interface metric for DVMRP reports.
ip igmp access- Control the multicast groups that hosts on the subnet serviced by an
group interface can join.
ip igmp immediate- Minimizes the leave latency of IGMP memberships and only one receiver
leave host is connected to each interface
ip igmp last- Configures the count to which the router sends IGMP group-specific host
member-query-count query messages.
ip igmp last-
Configures the frequency at which the software sends IGMP group
member-query-
specific host query messages.
interval
ip igmp querier- Configures the timeout time before the router takes over as the querier for
timeout the interface.
ip igmp query- Configures the frequency at which the software sends IGMP host query
interval messages.
ip igmp query-max-
Configures the maximum response time advertised in IGMP queries.
response-time
ip igmp static-non- Configures an interface as IGMP non-querier which will not send IGMP
querier query messages and thus will not be able to manage the IGMP hosts.
ip igmp static- Configures an interface as IGMP querier which will send IGMP query
querier messages and thus will be able to manage the IGMP hosts.
ip igmp snoop Enables IGMP snooping feature on the router.
Enables IGMP immediately leave feature which is the router immediately
ip igmp snoop
removes a port when it detects an IGMP version 2 leave message on that
fast-leave
port.
ip igmp snoop Configure the maximum number of multicast groups that a port can
group-number-limit belong to.
ip igmp snoop Specifies IGMP group membership time which defines how long a group
membership timeout will remain active on an interface in the absence of a group report.
ip igmp snoop
Adds a port as a member of a multicast group.
mgroup
(Continued)
Command Description
ip pim rp-register-
Set keep alive timer value to monitor PIM register message.
kat
ip pim spt-threshold
Causes all sources for the specified group to use the shared-tree.
infinity
ip pim sparse-mode Enables PIM-SM on a VLAN interface.
ip pim state-refresh
Disables PIM-DM the state refresh feature.
disable
ip pim state-refresh
Configures the origination interval for the state refresh control message.
origination-interval
show ip dvmrp
Displays DVMRP global parameters.
configuration
show ip dvmrp
Displays DVMRP interface information.
interface
show ip dvmrp
Displays DVMRP-neighbor information on a per-interface basis.
neighbor
show ip dvmrp prune Displays the DVMRP upstream prune state.
show ip dvmrp route Displays the DVMRP routing table contents.
Displays IGMP host members for a particular multicast group or for all
show ip igmp group
multicast groups
show ip igmp
Displays IGMP related information about an interface.
interface
Displays the multicast groups with receivers that are directly connected
show ip igmp snoop
to the router, and that were learned through IGMP snooping.
show ip igmp snoop display the list of the VLANs and ports which IGMP immediately leave
fast-leave feature is enabled on
Displays IGMP group membership time which defines how long a
show ip igmp snoop
group will remain active on an interface in the absence of a group
membership
report.
show ip igmp snoop Displays information on dynamically learned and manually configured
mrouter multicast router interfaces
show ip pim
Display the PIM-SM bootstrap router (BSR) information
bsr-router
show ip pim
Displays basic configuration information for PIM
configuration
show ip pim interface Displays information about interfaces configured for PIM
show ip pim neighbor Displays information about PIM neighbor.
(Continued)
Command Description
show ip pim rp
Displays all group-to-RP mappings of which the router is aware
mapping
show ip pim rp-hash Displays which RP is being selected for a specified group
This chapter describes how to configure the following routing protocols supported by the Corecess S5
System:
Configuring Static Route
Standard Route
The standard route consists of a network address of a destination, a network mask and an IP
address of next hop gateway. The standard route transmits packets that destination is a
particular network or host to the specified next hop router.
Loopback route
The loopback route consists of a network address of a destination, a network mask and an
index number of a loopback interface. The loopback route transmits packets that destination
is a particular network or host to the specified loopback interface. The loopback route is used
for testing of the loopback path.
Null Route
The null route consists of a network address of a destination, a network mask and an index
number of the null interface. If the null route cannot use the standard route, the null route is
used as a backup route for discarding traffic.
Command Description
The following example shows how to add the static route. The destination address is 192.0.0.0/8,
and the IP address of the next hop router is 195.1.1.1:
Command Description
configure terminal 1. Enter Global configuration mode.
Note: When you configure the VLAN interface route, the VLAN interface that is used as the
next hop should be enabled. If the VLAN interface is not enabled, the message of ‘%
Malformed gateway or interface not found.’ is displayed on the console
terminal. To enable the VLAN interface, use interface vlan id <vlan-id> command
in Global configuration mode.
The following example shows how to configure the static route that uses the VLAN as the next
hop:
Command Description
configure terminal 1. Enter Global configuration mode.
Note: When you configure the loopback route, the loopback interface should be enabled. If
the loopback interface is not enabled, the message of ‘% Malformed gateway or
interface not found.’ is displayed on the console terminal. To enable the loopback
interface, use interface loopback id <index> command in Global configuration
mode.
The following example shows how to configure the static route that transmits the packet to the
loopback interface.
Command Description
configure terminal 1. Enter Global configuration mode.
Note: When you configure the null route, the null interface should be enabled. If the null
interface is not
enabled, the message of ‘% Malformed gateway or interface not found.’ is
displayed on the console terminal. To enable the null interface, use interface null id
<index> command in Global configuration mode.
The following example shows how to configure the static route that discards packets.
Command Description
configure terminal 1. Enter Global configuration mode.
2. Specify IP address of the default gateway.
ip route default
<gateway> [<distance>] <gateway-address> IP address of the default gateway
<distance> Administrative distance of the route (1-255)
end 3. Return to Privileged mode.
show ip route static 4. Verify the route configuration.
Configuring BGP
BGP(Border Gateway Protocol) Overview
BGP Introduction
The BGP (Border Gateway Protocol) is an external gateway protocol to exchange routing
information among IP routers that are in the different AS (Autonomous System). The BGP is
defined in RFC 1105, and the current version is BGP4 which is defined in RFC 1771. The BGP is
generally used for ISP (Internet Service Provider). The BGP is used not only in huge commerce
networks but also in multi home networks.
An AS is a set of network under the same routing policy and management policy, and an
enterprise intranet that consists of several networks with the same policy is an example of AS.
Routers in the same AS can use internal gateway protocols, such as RIP or OSPF, to exchange
routing information. But if the routers exchange information with routers that are in the
different AS, the routers should use external gateway protocols such as BGP4.
The following picture shows the example of BGP-4 AS. Each AS has three BGP-4 routers. BGP-4
routers of the same AS exchange information using IBGP, and BGP-4 routers of the different AS
exchange information using EBGP. Each router also uses internal gateway protocols. Routers of
AS 1 are OSPF routers, and routers of AS 2 are RIP routers. You can configure the Corecess S5
System to redistribute routes among BGP4, RIP and OSPF, and also to redistribute static routes.
The BGP4 route table of the Corecess S5 System can have several routes for the same destination,
and these routes are received from other BGP4 neighbors. The BGP4 neighbor is a router that is
executing BGP4 routing. The BGP neighbor uses TCP port 179 to transmit information. If the
Corecess S5 System is configured to the BGP router, the network administrator should define
BGP4 neighbors first.
Even the BGP4 routing table of routers can have several routes, but the BGP4 protocol evaluates
each route and chooses an optimal route to transmit the IP route table. If a problem occurs in
the route, the BGP4 protocol updates route information of the IP route table.
Net Description number (Prefix): This value consists of the network mask bit and the IP
address and is displayed as the form of ‘address/mask’. For example, ‘192.215.129.0/18’
means that the network mask of eighteen bit is applied to the IP address of ‘192.215.129.0’.
When the BGP4 router transmits routes to neighbor routers, the routes are expressed with
the form.
AS Path: The AS path of a list of AS that routes are passed. The BGP4 router can use the AS
path to detect or remove the routing loop. For example, if the route that is received from the
BGP4 router includes the AS number of the current router, the router detects the loop and
does not add the route to its BGP4 table.
Path Attribute: The path attribute is the list of parameters that displays the attribute of route
(ORIGIN, AS-PATH, NEXT-HOP, MED, local- pref. and, aggregator, etc.).
When the Corecess S5 System connects a BGP session with neighbor routers (BGP peer)
successfully, the Corecess S5 System exchanges the BGP routing table to the neighbor. After this
initial exchange of information, the Corecess S5 System only exchanges the UPDATE message
to inform new routes, changed routes and unavailable routes.
The BGP router transmits the KEEPALIVE message periodically to maintain the BGP session
with neighbor routers.
BGP selects only one path as the best path. When the path is selected, BGP puts the selected
path in its routing table and propagates the path to its neighbors. BGP uses the following
criteria, in the order presented, to select a path for a destination:
1. If the path specifies a next hop that is inaccessible, drop the update.
3. If the weights are the same, prefer the path with the largest local preference.
4. If the local preferences are the same, prefer the path that was originated by BGP running on
this router.
5. If no route was originated, prefer the route that has the shortest AS-path.
6. If all paths have the same AS-path length, prefer the path with the lowest origin type (where
IGP is lower than EGP, and EGP is lower than Incomplete).
7. If the origin codes are the same, prefer the path with the lowest MED attribute.
8. If the paths have the same MED, prefer the external path over the internal path.
9. If the paths are still the same, prefer the path through the closest IGP neighbor.
Generally, the important element is the length of AS_path because the elements about the BGP
path such as weight or the local preference are same.
Enabling BGP
To enable the BGP protocol on the Corecess S5 System, execute the following tasks :
1. Enabling BGP Protocol
2. Specifying Local AS Number
3. Specifying BGP Network
To enable the BGP protocol and specify the BGP network, use the following commands.
Command Description
configure terminal 1. Enter Global configuration mode.
2. Enable BGP process on the system.
router bgp <as-num>
<as-num>: AS (Autonomous System) number (1 ~ 65535)
3. Specifies the networks to be advertised by the BGP and multi protocol
BGP routing processes.
network <network- <network-num>: Network that BGP or multi protocol BGP will
num>/<M> [multicast | advertise. This network should be connected directly or a route to
unicast multicast] the network specified must be present in the routing table.
<M>: Network or sub-network mask
The following example enables BGP process for autonomous system 100 and sets up network
200.10.10.0 to be included in the BGP updates:
# configure terminal
(config)# bgp router 100
(config-router)# network 200.10.10.0/24
(config-router)#
To remove a routing process, use the no router bgp command in Global configuration mode.
The BGP and OSPF routing protocol should use a router ID to identify each router on the
network. Therefore, the router ID should be unique. By default, the Corecess S5 System uses the
IP address of the loopback interface that has the lowest index number for the router ID. If the
loopback interface is not defined in the Corecess S5 System, the lowest number of the interface
IP address that is defined in the Corecess S5 System is used for the router ID.
The Corecess S5 System uses the same router ID as the one of BGP and OSPF. Therefore, if
OSPF is already configured in the Corecess S5 System, the router ID of OSPF is used. If OSPF is
not configured in the system, the default router ID or the static router ID can be assigned.
To specify the router ID in the Corecess S5 System, use the following commands.
Command Description
configure terminal 1. Enter Global configuration mode.
The following example shows how to specify the static router ID.
# configure terminal
(config)# router bgp 100
(config-router)# bgp router-id 1.1.1.1
(config-router)#
If you change the router ID of the BGP network that is already operating, the new ID is applied
after system rebooting or BGP process restarting. To restart BGP process manually, use the
clear ip bgp command.
Two BGP routers become neighbors once they establish a TCP connection between each other.
You should specify the IP address and AS number of the neighbor because the BGP protocol
does not search neighbors automatically to exchange routing information.
To specify a BGP neighbor, use the following command in BGP configuration mode:
Command Description
<ip-address>: IP address of the neighbor.
neighbor <ip-address>
<as-num>: AS (Autonomous System) number which the neighbor
remote-as <as-num>
belongs to (1 ~ 65535).
The following example adds BGP neighbors to exchange BGP routing information in each
router (RTA, RTB, RTC, and RTD):
AS100 AS300
IBGP
AS200
RTA
(config)# router bgp 100
(config-router)# neighbor 170.16.1.2 remote-as 200
RTB
(config)# router bgp 200
(config-router)# neighbor 170.16.1.1 remote-as 100
(config-router)# neighbor 120.10.1.2 remote-as 200
RTC
(config)# router bgp 200
(config-router)# neighbor 190.10.1.2 remote-as 300
(config-router)# neighbor 120.10.1.1 remote-as 200
RTD
(config)# router bgp 300
(config-router)# neighbor 190.10.1.1 remote-as 200
There may be a lot of neighbors that should consist of the same update policy such as route map,
distribute list, filter list and update source. The neighbor can group together for the simple
configuration and efficiency, and the group is called ‘peer group.
With the BGP peer group, you can set the same parameters of BGP neighbors once. Also, you
can save flash memory because the fewer configuration commands are saved into the backup
configuration file.
All parameters of BGP neighbor can be set in the peer group. When a neighbor is added in the
peer group, the neighbor has the same parameter attribute that is set in the peer group. If a
parameter value is not set in the peer group, or each neighbor is not set a parameter, the
neighbor uses the default parameter value.
You should configure the peer group before a neighbor is added in the peer group.
When the parameter values that are applied to the peer group are removed, if the parameter values are
not set to each neighbor, the default values are set to the neighbor. In this case, the values that are set
to each router are applied to the router, and the default values are applied to other routers.
When you add a neighbor to the peer group, you cannot configure the following parameters in the
neighbor.
- Default-information-originate
- Next-hop-self
- route map (Outbound)
- filter list (Outbound)
- distribute list (Outbound)
- prefix list (Outbound)
- Remote AS
- Route reflector client
- Send community, Timers
- Update source
If you change the outbound parameter of each neighbor, remove neighbors from the peer group. In
this case, you cannot add the neighbors to the same peer group again and can add the neighbors to the
different peer group. Neighbors in the peer group should have the same value of outbound parameters.
If you change the outbound parameter values of all neighbors to the same values in the peer group,
change the parameters of the peer group. In this case, you do not need to remove neighbors and
change each parameter.
If you set the outbound parameter for the peer group, the parameter is applied to all neighbors in peer
group automatically.
When you add a neighbor to the peer group, the system software removes all outbound parameters of
the neighbor from the current configuration. Thus, if you save the current system configuration to the
backup configuration file, the backup configuration file does not include outbound parameters for
each neighbor in the peer group. The only outbound parameters that are included in the backup
configuration file are related to the peer group. But the current configuration file and the backup
configuration file can have not only each of outbound parameter but also the parameter of neighbors
in the peer group.
The following example shows how to define the EBGP peer group named ‘external’. Each
member of the peer group is in the different AS (AS 200, 300, 400).
After the configuration of the BGP neighbor or the BGP peer group, you can set the following
BGP neighbor parameters.
Parameter Description
capability route-
Set the router to request route refresh dynamically with BGP neighbor.
refresh
default-originate Allow to use the default route of the BGP neighbor.
Description Add a simple explanation for the BGP neighbor.
Filter routing information that is transmitted or received to the BGP neighbor
distribute-list
depending on the condition of the access list.
ebgp-multihop Connect the router to external node.
Filter routing information that is transmitted or received to the BGP neighbor
filter-list
using the AS-path access list.
Specify the maximum number of prefix that can be received from the BGP
maximum-prefix
neighbor.
Change the next hop of the route to its IP address when the route is transmitted
next-hop-self
to the specified BGP neighbor.
Set a TCP port that is used when connection between the BGP neighbor and the
port
BGP session.
Filter routing information that is transmitted or received to the BGP neighbor
prefix-list
using the Prefix list.
Filter route that is transmitted or received to the BGP neighbor using the route
route-map map or change the attribute of the route (weight, community, local preference,
metric, next hop, etc.)
route-reflector- Set a local router to the BGP route reflector of the specified neighbor. The route
client reflector transmits the route that is learned from other router to other routers.
Transmit the community attribute together when the route is transmitted to the
send-community
specified BGP router.
shutdown Remove all sessions and routing information for the BGP neighbor.
soft-reconfiguration Apply the changed configuration for the BGP neighbor.
timers Set the timer value for the BGP neighbor.
Allow to specify the BGP neighbor using the loopback interface instead of
update-source
physical interface from the other BGP router.
version Specify the BGP version for the communication to the BGP neighbor.
weight Specify the value of weight to the received route that is from the BGP neighbor.
The following section explains how to configure the BGP neighbor parameters.
Command Description
neighbor {<ip-address> |
<ip-address> IP address of the BGP neighbor
<peer-group-name>}
capability route-refresh <peer-group-name> Name of the BGP peer group
When the routing policy of a particular node is changed, the node requests the latest route
information to BGP neighbor. If you use this command, you can set the local router to renew the
route information dynamically with the specified BGP neighbor.
The BGP router, which supports the route refresh, requests the route refresh with the OPEN
message. The BGP router only transmits the route refresh information to the BGP neighbor that
requested the route information. If a BGP router does not support the route refresh, the request
is ignored, but a BGP router that supports the route refresh transmits its RIB (Routing
Information Base) to response the request.
The following example shows how to set the routers to request the route refresh.
Command Description
The following example shows how to set the BGP router to transmit the default route entry .
Command Description
<ip-address> IP address of the BGP neighbor
neighbor {<ip-address> |
<peer-group-name> Name of the BGP peer group
<peer-group-name>}
<string> Explanation for the BGP neighbor (Maximum 80
Description <string>
character)
The following example shows how to add an explanation to the BGP neighbor.
You can not apply filtering lists of the access list and IP prefix to the same BGP neighbor.
Command Description
<ip-address> IP address of the BGP neighbor
<access-list-number> Number of an access list to apply (500 ~
neighbor <ip-address>
999)
distribute-list
in Apply the access list when receiving the routing information
<access-list-number>
from the specified BGP neighbor.
{in | out}
out Apply the access list when transmitting the routing
information from the specified BGP neighbor.
The following example shows how to set filtering with access list. When the BGP router in AS
100 receives routing information from the BGP neighbor that IP address is 163.130.0.1, the
information is filtered depending on the condition of the access list (500).
The following example shows how to set filtering with access list. When the BGP router in AS
100 transmits routing information from the BGP neighbor that IP address is 163.130.0.1, the
information is filtered depending on the condition of the access list (500).
Command Description
<ip-address> IP address of the BGP neighbor
<peer-group-name> Name of the BGP peer group
neighbor {<ip-address> |
<route-map-name> Name of the route map to apply
<peer-group-name}
in Apply the route map to the receiving route from the BGP
route-map <rout-map-
neighbor.
name> {in | out}
out Apply the route map to the transmitting route from the BGP
neighbor.
You can filter a particular route or the attribute of the route with the route map.
On the network configuration as above, RTA receives information for the local network of AS
200 and the network of AS 300 through RTB. If you want RTA to receive information only for
the local network of AS 200 and want to set the weight value of the received route to 20, use the
neighbor route-map command.
First, define the route map (map1) and the AS-path access list (path1) as follows:
Command Description
The following example shows how to filter the route using the AS-path access list.
Command Description
You can configure the maximum number of 1000 IP prefix list filters in the Corecess S5 System.
To configure the IP prefix list, use the ip prefix-list command in Global configuration
mode.
The following example applies the prefix list named prefix ii to incoming advertisements to
neighbor 120.10.1.1:
Specifying Multihop
If you specify an external node to the BGP neighbor for the EBGP connection, use neighbor
ebgp-multihop command in BGP configuration mode.
Command Description
When executing the neighbor ebgp-multihop command, you can specify the number of hop (1 ~
255) between the specified neighbor and external nodes that allow the EBGP connection. The
number of hop is called TTL. If you set TTL to 1, you can not specify the node that over two
routers is in the connection to the EBGP neighbor.
The following example shows that two interface set the TCP connection for the BGP routing.
RTA
(config)# router bgp 100
(config-router)# neighbor 180.225.1.1 remote-as 300
(config-router)# neighbor 180.225.1.1 ebgp-multihop
(config-router)#
RTB
(config)# router bgp 300
(config-router)# neighbor 172.16.1.2 remote-as 100
(config-router)#
Command Description
<ip-address> IP address of the BGP neighbor
<peer-group-name> Name of the BGP peer group
neighbor {<ip-address> |
<maximum> Maximum number of the prefix (1 ~ 4294967295)
<peer-group-name}
<threshold> Percentage value (0 ~ 100%). The default value is
maximum-prefix <maximum>
75%. If the number of prefix exceeds the maximum number that is
[<threshold>] [warning-
set in <maximum>, the warning log is stored.
only]
warning-only the number of prefix exceed the value of
<maximum> and <threshold>, the warning log is stored.
The following example shows how to set the maximum number of prefix.
Command Description
neighbor {<ip-address> |
<ip-address> IP address of the BGP neighbor
<peer-group-name}
next-hop-self <peer-group-name> Name of the BGP peer group
For an example of the network as follows, network information of 60.1.1.0 is transmitted to RTB
and RTC through RTA. At this time, the next hop of 60.1.1.0 is specified to 50.1.1.1. After RTB
receives network information of 60.1.1.0 from RTA, RTB transmits network information to RTC
with next hop information.
When the network of 20.1.1.0 transmits a packet to the network of 60.1.1.0, RTC try to connect to
50.1.1.1, which is the next hop of 60.1.1.0. Since RTC cannot be connected to the network of
50.1.1.1, the packet is dropped. To prevent above situation, use the neighbor next-hop-
self command. If the neighbor 10.1.1.2 next-hop-self command is executed in RTB,
when network information of 60.1.1.0 is transmitted from RTB to RTC, RTB changes the next
hop to 10.1.1.1, which is its own IP address. Then, when the packet is transmitted from RTC to
the network of 60.1.1.0, RTC is connected to 10.1.1.1, and the packet can be transmitted to the
network of 60.1.1.0.
When the neighbor next-hop-self command is executed, if the BGP peer group is set as a
parameter, the command is applied to all members of the BGP peer group. However, the value
by IP address of the BGP neighbor is prior than the value by the BGP peer group.
The following example shows how to change the next hop to its own IP address.
Command Description
In normal cases, all Interior Border Gateway Protocol (IBGP) speakers in an autonomous system
must be fully meshed. By utilizing the route reflector concept, not all IBGP speakers need be
fully meshed. In the route reflector model, an internal BGP peer is configured to be a route
reflector responsible for passing IBGP learned routes to IBGP neighbors. This scheme eliminates
the need for each router to talk to every other router.
To configure the local router as the route reflector and the specified neighbor as one of its clients,
use the following command in BGP configuration mode:
Command Description
In the following example, the local router that belongs to autonomous system 100 is a route
reflector. It passes learned IBGP routes to the neighbor at 192.20.16.1:
Command Description
<ip-address> IP address of the BGP neighbor
neighbor {<ip-address> | <peer-group-name> Name of the BGP peer group
<peer-group-name} both Transmit the extend community and standard community
send-community [both | of the BGP route
extended | standard] extended Transmit the extend community of the BGP route
standard Transmit the standard community of the BGP route.
The following example shows how to use the neighbor send-community command:
To shut down the neighbor, use the neighbor shut down command in BGP configuration mode.
Command Description
neighbor {<ip-address> |
<ip-address> IP address of the BGP neighbor
<peer-group-name}
shutdown <peer-group-name> Name of the BGP peer group
After the configuration of the BGP neighbor parameters, use the no neighbor shutdown
command to connect the session with the neighbor again.
The following example shows how to shut down the connected session or routing information.
The soft reconfiguration stores all BGP tables from the BGP neighbor into the memory. When
applying new policy, the soft reconfiguration uses tables which are in the memory instead the
session reset or receiving tables from the BGP neighbor.
If the soft reconfiguration is set in the Corecess S5 System, and the BGP neighbor supports the
dynamic refresh, the Corecess S5 System transmits the refresh message to neighbors. But, if the
BGP neighbor does not support the dynamic refresh, the Corecess S5 System resets the session
of neighbors.
This is a process to confirm that the Corecess S5 System has complete tables, and this process
occurs once when you set the soft reconfiguration feature to operate.
Command Description
neighbor {<ip-address> |
<peer-group-name} <ip-address> IP address of the BGP neighbor
soft-reconfiguration <peer-group-name> Name of the BGP peer group
inbound
The following example shows how to set the soft reconfiguration feature to operate.
To apply new policy, use the clear ip bgp command in Privileged mode. Then, the Corecess S5
System updates tables dynamically comparing to the stored table and route policy.
Setting Timer
There are three timer of the BGP neighbor as follows:
Waiting time that the Corecess S5 System tries to reconnect with the BGP 60
connect
neighbor after disconnection of BGP neighbor (0 ~ 65535 seconds) seconds
To set the timers of the BGP neighbor, use the following commands in BGP configuration mode.
Command Description
<ip-address> IP address of the BGP neighbor
neighbor {<ip-address> |
<peer-group-name> Name of the BGP peer group
<peer-group-name>}
<keepalive-timer> Value of the keepalive timer (0 ~ 65535
timer <keepalive-timer>
seconds)
<hold-timer>
<hold-timer> Value of the Hold timer (0 ~ 65535 seconds)
neighbor <ip-address> <ip-address> IP address of the BGP neighbor
timers connect <connet- <connet-timer> Value of the Connect timer (0 ~ 65535
timer> seconds)
The following example shows how to set timers of the BGP neighbor.
(config)# router bgp 100
(config-router)# neighbor 190.10.1.14 timers 50 150
(config-router)# neighbor 190.10.1.14 timers connect 100
Command Description
neighbor {<ip-address>| <peer-
<ip-address> IP address of the BGP neighbor
group-name}
<peer-group-name> Name of the BGP peer group
update-source {loopback id
<loopback-id> Loopback interface ID (1 ~ 32)
<loopback-id> | port
<slot>/<port> Number of slot/port
gigabitethernet <slot>/<port>|
<vlan-id> VLAN ID (1 ~ 4095)
vlan id <vlan-id>|
<vlan-name> VLAN name
vlan name <vlan-name>}
The loopback interface is an interface that IP address is assigned, and is not related to a physical
port. Since the physical port is not assigned, the loopback interface cannot transmit and receive
a packet.
If the loopback is used when a neighbor is specified using the neighbor remote-as
command, the neighbor should allow to use its loopback interface using the neighbor
update-source command.
The following example shows how to set a neighbor using the loopback interface.
RTA
(config)# router bgp 100
(config-router)# neighbor 192.10.1.1 remote-as 100
RTB
(config)# router bgp 100
(config-router)# neighbor 172.16.1.2 remote-as 100
(config-router)# neighbor 172.16.1.2 update-source vlan id 1
Command Description
The weight is an attribute that is set to the route that is registered in a local router, and is not
transferred to other routers. If the router learns several routes for the same destination, the
route that has higher weight value is chosen.
The default weight that is learnt from other BGP neighbors is ‘0’, and the default weight that is
learnt from local routers is ‘32768’.
The following example shows how to configure routes to set weight.
Command Description
<ip-address> IP address of the BGP neighbor
<peer-group-name> Name of the BGP peer group
neighbor {<ip-address> |
<version> BGP version (4, 4-)
<peer-group-name>}
- 4 : BGP version 4
version <version>
- 4- : Multi protocol extension version of BGP version 4
(previous version)
The following example shows how to set the BGP protocol to BGP version 4.
To allow the comparison of the MED for paths from neighbors in different AS, use the bgp
always-compare-med command in BGP configuration mode.
The following example shows how to set the BGP router to compare paths from the different AS
when selecting the path.
The following example shows that the BGP router regards missing MED as assigning the
infinity value so that the BGP router does not choose the path.
By default, the Corecess S5 System considers the as-path length when selecting a route.
The following example shows how to configure the route to ignore as-path length in selecting a
route.
The following example shows how to compare similar routes and chose the best path that has
the lowest ID.
Parameter Description
Distance is used to compare routes of different protocols for the same
Distance destination. It can be changed that the proper route is chosen depending on
the network.
When routes are redistributed to other routing protocols, you can set route
redistribution metric
metric values to be changed.
bgp client-to-client
Set BGP neighbors not to be operated as route reflectors.
reflection
Cluster-id Configure the cluster ID if the BGP cluster has more than one route reflector.
default ipv4-unicast Enable the IP version 4 unicast address family on all neighbors
Default local-
Change default local preference value when selecting exit point.
preference
Configure a router to deny an update received from an external BGP router
Enforce-first-as that does not list its AS number at the beginning of the AS_SEQUENCE in the
incoming update
Scan time Configure scanning interval of BGP routers for next hop validation
Setting Distance
Distance is a value to compare routes of different routing protocols for the same destination.
The lower value is preferred . To change the distance value for topology or retribution, use the
distance command in BGP configuration mode.
Command Description
<distance> Distance of the BGP route to specify newly (1 ~ 255)
distance <distance>
<ip-address>/<M> IP address/subnet mask of the network that the
<ip-address>/<M>
BGP router is included.
[<access-list-num>]
<access-list-num> Number of access list to apply (500 ~ 999)
Command Description
redistribute <protocol> <protocol> Type of route to redistribute
[metric <metric>] <metric> metric value of route entry (1 ~ 16)
[route-map <route-map-name>] <route-map-name> Name of route map to be applied
The following example shows how to change metric of RIP route that is satisfied to the
condition of route map (rip-map) to 200.
The following example shows how to set the route reflector not to operate.
Setting Cluster ID
To configure the cluster ID if the BGP cluster has more than one route reflector, use the bgp
cluster-id command.
The following example shows how to enable IP version 4 unicast address family on all neighbor.
To change the default local preference value, use the bgp default local-preference
command in BGP configuration mode.
Command Description
bgp default local- <value> Value of default local preference (0 ~ 4294967295). The higher
preference <value> value is more preferred.
Setting enforce-first-as
To configure a router to deny an update received from an external BGP router that does not list
its AS number at the beginning of the AS_SEQUENCE in the incoming update, use the bgp
enforce-first-as command in BGP configuration mode.
The following example shows how to configure a router to receive update message.
Command Description
bgp scan-time
<interval> Time interval (5 ~ 60 seconds)
<interval>
By default, the default scanning interval is 60 seconds in the Corecess S5 System. The following
example shows how to set the scanning interval.
The following example show how BGP routers execute load balancing by the Equal Cost
Multipath Routing Protocol
To display the route entry of the BGP routing table, use the show ip bgp command in
Privileged mode.
# show ip bg
When executing the show ip bgp command, the following entry information of the BGP route:
Field Description
Version number of the BGP routing table. This number is incremented whenever
BGP table version
the table changes. The default value is 0.
local router ID IP address of the router
Status of the table entry. The status is displayed at the beginning of each line in
the table. It can be one of the following value:
s – The table entry is suppressed.
Status codes
* - The table entry is valid.
> - The table entry is the chosen path (the shortest distance)
i – The table entry was learned via an IBGP session.
Origin of the entry. The origin code is placed at the end of each line in the table. It
Origin codes can be one of the following values:
i – Path originated from an IGP(Interior Gateway Protocol) and was
To display information of the BGP route attribute, use the show ip bgp attribute-info
command in Privileged mode.
When executing the show ip bgp attribute-info command, the following information of
the BGP route attribute is displayed.
Field Description
Origin of the entry. The origin code is placed at the end of each line in the table. It can
be one of the following values:
i – Path originated from an IGP(Interior Gateway Protocol) and was registered
with a network command in BGP configuration mode.
Origin codes
e – Path originated from an EBGP neighbor
? – Origin of the path is not clear. Usually, this is redistributed into BGP from
an IGP.
= – ECMP(Equal Cost Multi Path)
IP address of the next system that is used when forwarding a packet to the
Next Hop destination. An entry of 0.0.0.0 indicates that the router has some non-BGP route to
this network.
Metric Metric value used in internal of AS.
Local preference value of the route (default: 100). This value is specified with the bgp
LocPrf
default local-preference command in BGP configuration mode.
Weight Weight value of the route
AS paths to the destination network. There can be one entry in this field for each AS
Path
in the path.
To display CIDR (Classless Interdomain Routing) routes, use the show ip bgp cidr-only
command in Privileged mode.
Field Description
Version number of the BGP routing table. This number is incremented whenever
BGP table version
the table changes. The default value is 0.
local router ID IP address of the router
Status of the table entry. The status is displayed at the beginning of each line in the
table. It can be one of the following value:
s – The table entry is suppressed.
Status codes * - The table entry is valid.
> - The table entry is the chosen path (the shortest distance)
i – The table entry was learned via an IBGP session.
= – ECMP(Equal Cost Multi Path)
Origin of the entry. The origin code is placed at the end of each line in the table. It can
be one of the following values:
i – Path originated from an IGP(Interior Gateway Protocol) and was
Origin codes registered with a network command in BGP configuration mode.
e – Path originated from an EBGP neighbor
? – Origin of the path is not clear. Usually, this is redistributed into BGP from
an IGP.
Network IP address of destination.
IP address of the next system that is used when forwarding a packet to the
Next Hop destination. An entry of 0.0.0.0 indicates that the router has some non-BGP route to
this network.
Metric Metric value used in internal of AS.
Local preference value of the route (default: 100). This value is specified with the
LocPrf
bgp default local-preference command in BGP configuration mode.
Weight Weight value of the route
AS paths to the destination network. There can be one entry in this field for each
Path
AS in the path.
To display information of all BGP community, use the show ip bgp community-info
command.
When executing the show ip bgp community-info command, the following information of the
BGP community is displayed.
Field Description
To display routes that belong to specified BGP communities, use the show ip bgp
community local-AS command in Privileged mode.
When executing the show ip bgp community local-AS command, the following
information of BGP routes that belong to specified communities is displayed:
Field Description
Version number of the BGP routing table. This number is incremented whenever
BGP table version
the table changes. The default value is 0.
local router ID IP address of the router
Status of the table entry. The status is displayed at the beginning of each line in
the table. It can be one of the following value:
s – The table entry is suppressed.
Status codes * - The table entry is valid.
> - The table entry is the chosen path (the shortest distance)
i – The table entry was learned via an IBGP session.
= – ECMP(Equal Cost Multi Path)
Origin of the entry. The origin code is placed at the end of each line in the table. It
can be one of the following values:
i – Path originated from an IGP(Interior Gateway Protocol) and was
Origin codes registered with a network command in BGP configuration mode.
e – Path originated from an EBGP neighbor
? – Origin of the path is not clear. Usually, this is redistributed into BGP
from an IGP.
Network IP address of destination.
IP address of the next system that is used when forwarding a packet to the
Next Hop destination. An entry of 0.0.0.0 indicates that the router has some non-BGP route
to this network.
Metric Metric value used in internal of AS.
Local preference value of the route (default: 100). This value is specified with the
LocPrf
bgp default local-preference command in BGP configuration mode.
Weight Weight value of the route
AS paths to the destination network. There can be one entry in this field for each
Path
AS in the path.
To display routes that are permitted by the BGP community list, use the show ip bgp
community-list command in Privileged mode.
The following example shows how to display information of the route that is in the community
list of 20.
When executing the show ip bgp community-list command, the following information is
displayed:
Field Description
Version number of the BGP routing table. This number is incremented whenever
BGP table version
the table changes. The default value is 0.
local router ID IP address of the router
Status of the table entry. The status is displayed at the beginning of each line in
the table. It can be one of the following value:
s – The table entry is suppressed.
Status codes * - The table entry is valid.
> - The table entry is the chosen path (the shortest distance)
i – The table entry was learned via an IBGP session.
= – ECMP(Equal Cost Multi Path)
Origin of the entry. The origin code is placed at the end of each line in the table. It
can be one of the following values:
i – Path originated from an IGP(Interior Gateway Protocol) and was
Origin codes registered with a network command in BGP configuration mode.
e – Path originated from an EBGP neighbor
? – Origin of the path is not clear. Usually, this is redistributed into BGP
from an IGP.
To display routes that are matched with condition of access list, use the show ip bgp
filter-list command in Privileged mode.
The following example shows how to display routes that is filtered with condition of as-path
access list named 2 in the BGP routing table.
When executing the show ip bgp filter-list command, the following information is
displayed:
Field Description
BGP table Version number of the BGP routing table. This number is incremented whenever
version the table changes. The default value is 0.
local router ID IP address of the router
Status of the table entry. The status is displayed at the beginning of each line in the
table. It can be one of the following value:
s – The table entry is suppressed.
Status codes * - The table entry is valid.
> - The table entry is the chosen path (the shortest distance)
i – The table entry was learned via an IBGP session.
= – ECMP(Equal Cost Multi Path)
Origin of the entry. The origin code is placed at the end of each line in the table. It can
be one of the following values:
i – Path originated from an IGP(Interior Gateway Protocol) and was
Origin codes registered with a network command in BGP configuration mode.
e – Path originated from an EBGP neighbor
? – Origin of the path is not clear. Usually, this is redistributed into BGP from
an IGP.
Network IP address of destination.
IP address of the next system that is used when forwarding a packet to the
Next Hop destination. An entry of 0.0.0.0 indicates that the router has some non-BGP route to
this network.
Metric Metric value used in internal of AS.
Local preference value of the route (default: 100). This value is specified with the
LocPrf
bgp default local-preference command in BGP configuration mode.
Weight Weight value of the route
AS paths to the destination network. There can be one entry in this field for each
Path
AS in the path.
To display route information that is transmitted and received from the BGP neighbor, use the
show ip bgp neighbors command in Privileged mode.
The following example shows how to display routes that is transmitted to the neighbor of
172.16.232.178 using the show ip bgp neighbors advertised-routes command.
When executing the show ip bgp neighbors command, the following route information is
displayed.
Field Description
BGP table Version number of the BGP routing table. This number is incremented whenever
version the table changes. The default value is 0.
local router ID IP address of the router
Status of the table entry. The status is displayed at the beginning of each line in the
table. It can be one of the following value:
s – The table entry is suppressed.
Status codes * - The table entry is valid.
> - The table entry is the chosen path (the shortest distance)
i – The table entry was learned via an IBGP session.
= – ECMP(Equal Cost Multi Path)
Origin of the entry. The origin code is placed at the end of each line in the table. It can
be one of the following values:
i – Path originated from an IGP(Interior Gateway Protocol) and was
Origin codes registered with a network command in BGP configuration mode.
e – Path originated from an EBGP neighbor
? – Origin of the path is not clear. Usually, this is redistributed into BGP from
an IGP.
Network IP address of destination.
IP address of the next system that is used when forwarding a packet to the
Next Hop destination. An entry of 0.0.0.0 indicates that the router has some non-BGP route to
this network.
Metric Metric value used in internal of AS.
Local preference value of the route (default: 100). This value is specified with the
LocPrf
bgp default local-preference command in BGP configuration mode.
Weight Weight value of the route
AS paths to the destination network. There can be one entry in this field for each
Path
AS in the path.
To display information of all BGP paths that stored in the database, use the show ip bgp paths
command in Privileged mode.
When executing the show ip bgp paths command, the following information is displayed.
Field Description
Address Internal address where the path is stored.
Refcnt Number of routes using that path.
Path AS number path for this route, followed by the origin code for that route.
You can retrieve BGP routes, which a particular string is included in AS paths, using BGP
regular expression as follows:
. : Matches any single character.
* : Matches zero or more sequences of the character preceding the asterisk.
+ : Matches one or more sequence of the character preceding the plus sign.
? : Matches zero or one occurrence of the pattern.
^ : Matches the character null string at the beginning of an input string.
$ : Matches the character or null string at the end of an input string.
| : Matches one of the characters or character patterns on either side of the vertical bar.
space : Matches two of the characters or character patterns on both side of the space.
To display routes matching the AS path regular expression, use the show ip bgp regexp
command in Privileged mode.
Field Description
Version number of the BGP routing table. This number is incremented whenever
BGP table version
the table changes. The default value is 0.
Field Description
Origin of the entry. The origin code is placed at the end of each line in the table. It
can be one of the following values:
i – Path originated from an IGP(Interior Gateway Protocol) and was
Origin codes registered with a network command in BGP configuration mode.
e – Path originated from an EBGP neighbor
? – Origin of the path is not clear. Usually, this is redistributed into BGP
from an IGP.
Network IP address of destination.
IP address of the next system that is used when forwarding a packet to the
Next Hop destination. An entry of 0.0.0.0 indicates that the router has some non-BGP route
to this network.
Metric Metric value used in internal of AS.
Local preference value of the route (default: 100). This value is specified with the
LocPrf
bgp default local-preference command in BGP configuration mode.
Weight Weight value of the route
AS paths to the destination network. There can be one entry in this field for each
Path
AS in the path.
To display information of scan time, use the show ip bgp scan command in Privileged mode.
The scan time is time interval that BGP routers check valid next hop.
When executing the show ip bgp scan command, the following information is displayed.
Field Description
BGP Instance Status of Current BGP setting
BGP scan interval Time interval that the BGP router check valid next hop
Current BGP nexthop cache Cache for list that is registered as next hop
BGP connected route Network information that local interface of the BGP router is included.
To display the status of all BGP connections, use the show ip bgp summary command in
Privileged mode.
When executing the show ip bgp summary command, the following information is
displayed.
Field Description
BGP router
BGP router ID. The router identifier is specified by the bgp router-id command.
identifier
V BGP version
AS AS Number
TblVer Last version of the BGP database that was sent to the neighbor
The length of time that the BGP session has been in the Established state, or the
Up/Down
current status if not in the Established state.
Current state of the BGP session, and number of prefixes that have been received
from a neighbor or peer group. When the maximum number is reached, the string
State/PfxRcd
‘PrxRcd’ appears in the entry, the neighbor is shut down, and the connection is set to
Idle.
BGP Commands
The BGP commands in the Corecess S5 System are as follows:
Command Description
address-family Enter Address-family configuration mode to configure BGP routing session
ipv4 that used standard IPv4 multicast address prefix.
aggregate-address Specify aggregate route entry in BGP.
bgp always- Allow the comparison of the MED (Multi Exit Discriminator) for paths from
compare-med neighbors in different AS.
bgp bestpath
Ignore the AS path length when calculating preferred paths.
as-path ignore
bgp bestpath Compare identical routes received from external BGP peers during the best
compare-routerid path selection process and select the route with the lowest router ID.
bgp bestpath med
Enable MED comparison among paths learned from confederation peers.
confed
bgp bestpath med
Set the infinity value to the missing MED so that the path cannot be chosen
missing-as-worst
bgp client-to-
Enable reflection of routes between route-reflection via a BGP route reflector.
client reflection
bgp cluster-id Configure the cluster ID if the BGP cluster has more than one route reflector.
bgp default
Enable the IP version 4 unicast address family on all neighbors
ipv4-unicast
bgp default local-
Change the default local preference value.
preference
bgp deterministic- Allow the comparison of the MED variable when choosing routes advertised
med by different peers in the same AS.
bgp equal-cost- Configuration for the purpose of load balancing for the traffic with Equal Cost
multipath Multipath BGP Routing
Configure a router to deny an update received from an external BGP router
bgp that does not list its AS number at the beginning of the AS_SEQUENCE in the
enforce-first-as incoming update, use the bgp enforce-first-as command in BGP configuration
mode.
bgp router-id Apply a fixed router ID to the BGP router.
bgp scan-time Configure scanning interval of BGP routers for next hop validation
bgp soft-restart-
Apply the changed BGP configuration to the system directly.
auto
Specify administrative distance of external route, internal routes and
distance bgp
local routes.
neighbor Enable Allow exchanging routing information to the specified BGP neighbor.
neighbor
capability Allow requesting route refresh dynamically with the specified BGP neighbor.
route-refresh
neighbor Allow a BGP speaker to send the default route 0.0.0.0 to a neighbor for use as a
default-originate default route.
neighbor
Add a simple explanation of a BGP neighbor.
Description
neighbor Filter the route information for the specified neighbor with the condition of the
distribute-list access list
neighbor Accept and attempt BGP connections to external peers residing on networks
ebgp-multihop that are not directly connected.
neighbor
Define BGP filter using access list.
filter-list
neighbor maximum- Specify the maximum number of prefix that a local router can be received from
prefix BGP neighbors.
neighbor Configure the router as the next hop for a BGP-speaking neighbor or peer
next-hop-self group.
neighbor
Configure BGP peer group.
peer-group
Set TCP port for the connection between the specified BGP neighbor and the
neighbor port
BGP session.
neighbor Apply routes that are received and sent from the specified BGP neighbor to the
prefix-list specified prefix list.
neighbor remote-as Define BGP neighbors.
Apply a route map to incoming or outgoing routes for filtering or changing
neighbor route-map
attributes.
neighbor route-
Configure the router as a BGP route reflector.
reflector-client
neighbor send-
Send the community attribute with the route to the BGP neighbor.
community
Remove all operating sessions and routing information for the specified BGP
neighbor shutdown
neighbor.
neighbor soft-
Apply the changed configuration to the system for the specified BGP neighbor.
reconfiguration
neighbor timers Set timer values for the specified BGP neighbor.
neighbor timers
Set the connect timer value for the specified BGP neighbor.
connect
neighbor Allow other BGP routers to specify the BGP neighbor using the loopback
update-source interface instead of their physical interface.
neighbor version Specify the BGP version for the communication of BGP neighbors.
Set the weight value to the route that is received from the specified BGP
neighbor weight
neighbor.
network Specify the networks to be advertised by the BGP.
network backdoor Set high route priority of the specified network.
redistribute Redistribute received routes of different routing protocols.
show ip bgp Display route entries of the BGP routing table.
show ip bgp
Display information of BGP route attributes.
attribute-info
show ip bgp
Display the CIDR(Classless Interdomain Routing) route.
cidr-only
show ip bgp
Display information of routes that is included in the specified BGP community.
community
show ip bgp
Display information of all BGP communities.
community-info
show ip bgp
Display routes that are permitted by the BGP community list.
community-list
show ip bgp
Display routes that are matched with condition of access list.
filter-list
show ip bgp Display route information that is transmitted and received from the BGP
neighbors neighbor
show ip bgp paths Display information of all BGP paths that stored in the database.
show ip bgp regexp Display routes matching the AS path regular expression.
show ip bgp scan Display information of scan time.
show ip bgp
Display the status of all BGP connections
summary
Configuring OSPF
OSPF (Open Shortest Path First) Overview
Introduction
OSPF (Open Shortest Path First) protocol is an internal gateway protocol that sends and
receives routing information in AS (Autonomous System). The Corecess S5 System supports
OSPF version 2.0 defined in RFC 2328.
OSPF protocol provides equal cost multipath routing that can transmit packets simultaneously
to a particular destination through more than one interface. Thus, OFPF is appropriate for
complicated networks.
OSPF protocol uses SPF (Shortest Path First) algorithm to select the shortest path. SPF algorithm
calculates status of network interface and path cost that is used in the interface and connected
network, and selects a path that has the lowest cost. SPF algorithm only delivers routing
information when the network is changed. Thus, unnecessary traffic is not delivered. Also, SPF
algorithm can control the complicated and sophisticated network.
OSPF protocol can divide a network to several regions and can communicate link status
information in limited regions. The limited region is called ‘area’. OSPF can limit appropriate
number of routers in the area to maintain the link status database.
OSPF protocol supports VLSM (Variable Length Subnet Mask). Thus, OSPF protocol can assign
and use IP address efficiently. OSPF protocol can save the router memory and bandwidth and
can improve performance because of communicating summarized information.
OSPF protocol has a topology to apply routing algorithm different from RIP protocol. The
largest topology is an AS (Autonomous System), and an AS is a group of networks that shares
the common routing policy and managed by one structure. An AS is divided to several areas,
and an area is a group of sequential networks and connected hosts. The network that connects
areas in an AS is called ‘backbone’.
The following picture shows the typical network structure of OSPF topology.
IR (Internal Router)
Routers connected directly to a network in a particular area (RTC, RTE)
BR (Backbone Router)
Routers connected to a backbone network. ABRs and routers that are included in a backbone
network are BRs (RTA, RTB, RTG).
Configuring OSPF
The following procedure describes how to configure OSPF routing protocol in the Corecess S5
System.
2. Setting Router ID
Set the router ID of the Corecess S5 System. The router ID is used to identify each router in
OSPF.
Set the Corecess S5 System to operate OSPF protocol, use the router ospf command in Global
configuration mode.
# configure terminal
(config)# router ospf
(config-router)#
When executing the above command, OSPF routing protocol operates and enter OSPF
configuration mode.
Set Router ID
A router ID is used to classify each router in OSPF. A router ID is needed to set the relation of
adjacent router or to control messages between copies of SPF algorithm.
To set a router ID in OSPF, use the router-id command in OSPF configuration mode.
Command Description
When the router ID of OSPF network that is already operating is changed, the new router ID is
applied directly to the system and is reconnected to adjacent routers. If you restart OSPF
process manually, use the clear ip ospf command.
If networks are increased, the size of link state database is increased, and required time is also
increased for calculating of the shortest path tree. Thus, it affects performance of total network.
To solve above problems, a network can be divided to several areas in OSPF protocol, and link
state information can be exchanged in the limited area.
The area 0 is a central area that receives link state information from each area and sends link
state information to each area again. The area 0 is called ‘backbone area’, and other areas are
called ‘leaf area’. The backbone area includes all ABR (Area Border Router). In the Corecess S5
System, several OSPF areas can be configured, but at least one area must be configured as
backbone.
There are stub area and NSSA except backbone area and leaf area in OSPF area. Features of stub
area and NSSA are as follows:
Stub area
Stub area does not receive LSA that notifies external network information, the traffic is
transmitted through the interface that is specified to the default route to external networks.
The area that is specified to the stub area can reduce size of topology database and memory
that is for the database.
selectively. NSSA is generally used to deliver external routing information to other areas.
This section describes how to configure OSPF area including stub areas and NSSAs.
Configuring Area
To define the interfaces on which OSPF runs and to define the area ID for those interfaces, use
the network area command in OSPF configuration mode.
Command Description
<network-address> IP address to operate OSPF routing
protocol.
network <network-
<area-id> Area that is to be associated with the OSPF address
address> area <area-id>
range. It can be specified as either a decimal value or as an IP
address.
The following example shows how to set the network of 172.16.1.1/32 and the network of
172.162.1/32 to operate OSPF protocol and how to specify interfaces of the two networks to be
included in the area 0.
# configure terminal
(config)# router ospf
(config-router)# network 172.16.1.1/32 area 0
(config-router)# network 172.16.2.1/32 area 0
For example, the area of 0.0.0.1 can be specified as the stub area in the following picture.
To define an OSPF stub area, use the following command in OSPF configuration mode.
Command Description
The following example shows how to specify the area of 0.0.0.1 as the stub area.
# configure terminal
(config)# router ospf
(config-router)# network 192.168.3.0/24 area 0.0.0.1
(config-router)# area 0.0.0.1 stub
Configuring NSSA
NSSA has the feature of stub area and allow incoming external routing information selectively.
NSSA is generally used to deliver external routing information to other areas.
For the following example, external routing information from RIP cloud must be passed
through the area of 0.0.0.5 to be delivered to other network in the domain. At this time, the area
of 0.0.0.5 becomes NSSA.
The following example shows how to set the area of 0.0.0.5 to the NSSA.
Argument Description
Default-information-originate Originate Type 7 default into NSSA area.
No-redistribution No redistribution into this NSSA area.
No-summary Do not send summary LSA into NSSA.
Translator-role NSSA-ABR Translator role.
To use route summarization in the Corecess S5 System, use the area range command in
OSPF configuration mode. The area range command can be only used in ABR.
Command Description
The following example shows how to summarize the host information of network from 160.10.8.0 to
160.10.15.0 in area 2. To specify one range of networks from 160.10.8.0 to 160.10.15.0, subnet mask
should be 255.255.248.0 which has twenty one of number 1.
Parameter Description
Default Route Information advertise a default route of an OSPF routing domain
change the specified OSPF distance value for topology property or
Distance
redistribution
Default Metric change the default metric value
Metric of External Route specify metric values depending on routing protocols
filter routes when transmitting route entries using access-list to other
Filtering List
protocols
Passive Interface Specify passive interface.
Refresh Timer Specify the refresh period of OSPF LSA database.
SPF Timer Set SPF (Shortest Path First) timer.
Command Description
default-information always Even if a default route is not configured, ASBR generates
originate [always] and advertises a default route.
[metric <metric>] <metric> Cost of the default route entry (1 ~ 16777214)
[metric-type <type>] <type> Type of external route (1, 2)
The following example shows how to configure a router to advertise a default route of an OSPF
routing domain to neighbor routers.
Setting Distance
Distance is a value that is used for comparing routes of different routing protocols that have the
same destination. The default value of the distance is 110 in the Corecess S5 System.
To change the specified OSPF distance value for topology property or redistribution, use the
distance command in OSPF configuration mode.
Command Description
distance <distance> <distance> Distance of OSPF route (1 ~ 255)
The following example shows how to specify the OSPF route distance of the OSPF router to 100
in area 1.
The default metric value of OSPF route is 10. To change the default metric value, use the
default-metric command in OSPF configuration mode.
Command Description
default-metric <number> <number> default metric value (0 ~ 16777214)
The following example shows how to change the default metric value of OSPF route to 4.
Command Description
There are two types of methods (type 1, type 2) to calculate cost in an external route. Type 1 of
an external route adds external cost and internal cost to calculate cost. Type 2 of an external
route only uses external cost. If there are two external routes that have the same destination,
OFPF chooses type 1 of the external route.
Cost of E1 = a + b + c
Cost of E2 = a
The following example shows how to change the metric value that is
advertised from BGP network to ‘10’, and how to set the route type to type 1.
Command Description
distribute-list <access-list-number> Number of the access list to apply
<access-list-number> out (500 ~ 999)
[<protocol>] <protocol> Protocol to transmit the route entry.
The following example shows how to filter routes matched the condition of access list 550.
Command Description
loopback id Specify the loopback interface that is used as the
passive interface.
passive-interface
<loopback-id> Loopback interface ID that is set to the passive
{loopback id
interface (1 ~ 32).
<loopback-id>|
port Specify the port that is set to the passive interface.
port gigabitethernet
<slot>/<port> Slot of the port/Number of the port
<slot>/<port>|
vlan Specify the VLAN interface that is set to the passive interface.
vlan id <vlan-id>|
<vlan-id> VLAN interface ID that is set to the passive interface (1 ~
vlan name
4094).
<vlan-name>}
<vlan-name> VLAN interface name that is set to the passive
interface.
The following example shows how to specify the VLAN interface that ID is 2 as the passive
interface.
Command Description
refresh timer <seconds> <seconds> Refresh period (10 ~ 1800 seconds)
The following example shows how to set the refresh period of OSPF LSA database to sixty
seconds.
Default
Timer Description
Value
Waiting time until calculating SPF after an OSPF router receives information of
5
delay changed topology. If the timer is set to ‘0’, calculation of SPF is immediately
Seconds
started when receiving the information.
Waiting time until calculation the next SPF after a SPF is calculated. If the
10
holdtime timer is set to ‘0’, calculation of the next SPF is immediately started after
Seconds
calculating the SPF.
To change values of the OSPF timers, use the timers spf command in OSPF configuration
mode.
Command Description
<delay-timer> Value of the delay timer (0 ~ 4294967295
timers spf <delay-timer> seconds)
<holdtime-timer> <holdtime-timer> Value of the Holdtime timer (10 ~ 1800
seconds)
The following example shows how to set the timers.
# configure terminal
(config)# router ospf
(config-router)# timers spf 10 20
All ABR must be connected to the OSPF backbone area either directly or indirectly. If an ABR is
not connected to the backbone area physically, the ABR can configure a virtual link with other
ABR that is connected to the backbone area physically in the same area.
RTA is an ABR that is not physically connected to the backbone area (area 0) as follows. To
connect RTA to the backbone, a virtual link should be configured between ATA and ARC using
area 1 (transit area). The virtual link should be defined in routers that are located in the end of
the link, and routers that are in transit area do not need any configuration about the virtual link.
To define the virtual link, use the area virtual-link command in OSPF configuration mode.
Command Description
<area-id> Area ID assigned to the transit area for the virtual link.
area <area-id> This can be either a decimal value or a valid IP address.
virtual-link <router- <router-id> Router ID that is connected to the virtual link.
id> [authentication- authentication-key <key> Set simple password method to be
key <key> | message- used when authenticating with neighbors, and specify the password.
digest-key <key-id> message-digest-key <key-id> md5 <key> Set MD5
md5 <key>] authentication method to be used when authenticating with
neighbors, and specify the password.
RTA
RTC
RTC(config)# router ospf
RTC(config-router)# area 0.0.0.2 virtual-link 10.0.0.1
Command Description
<area-id> Area ID assigned to the transit area for the virtual link.
area <area-id>
This can be either a decimal value or a valid IP address.
virtual-link <router-
<router-id> Router ID that is connected to the virtual link.
id>
dead-interval Time that hello packets are not seen before a
{dead-interval|
neighbor declares the router down. This value must be the same for
hello-interval|
all routers.
retransmit-interval|
hello-interval Time between the hello packets. This value
transmit-delay}
must be the same for all routers.
<seconds>
retransmit-interval Time between link-state advertisement
[{dead-nterval|
(LSA) retransmissions for adjacencies belonging to the interface. The
hello-interval|
value must be greater than the expected round-trip delay
retransmit-interval|
transmit-delay Estimated time required to send a link-state
transmit-delay}
update packet on the interface.
<seconds> ...]
<seconds> Time interval (1 ~ 65535 seconds)
To display OSPF configuration information, use the show ip ospf command in Privileged
mode.
# show ip ospf
When executing the show ip ospf command, the following information is displayed.
Field Description
Router ID OSPF route ID
Supports ... Number of types of service supported (type 0)
Whether RFC 1583 is used when calculating cost of summary route. If
RFC1583 Compatibility flag
the value is ‘disable’, RFC 2328 is used.
Waiting time until calculating SPF after a OSPF router receives
SPF schedule delay
information of changed topology
Hold time between two SPFs Waiting time until calculation the next SPF after a SPF is calculated.
Refresh timer Refresh period of LSA
Number of external LSA Number of external LSA
Number of areas attached to
Number of areas that this router is connected to.
this router
Area ID Area ID that this router is connected to.
Number of interfaces in this
Number of interfaces in this area
area
Number of fully adjacent
Number of fully adjacent neighbors in the area
neighbors in this area
SPF algorithm executed Number of calculation of SPF in the router of the Area
Number of LSA Number of LSA
This field is displayed when the area does not use authentication
Area has no authentication
method.
To display the routing table of ABR and ASBR, use the show ip ospf border-routers
command in Privileged mode.
Field Description
Area The area ID of the area from which this route is learned
SPF No Information of area in which the router is included such as number and address
To display OSPF database information, use the show ip ospf database command in
Privileged mode. You can specify several options with the show ip ospf database command,
and different database information is displayed depending on each option
Option Description
To display OSPF interface information, use the show ip ospf interface command in
Privileged mode.
When executing the show ip ospf interface command, the following information about
OSPF interface is displayed.
Field Description
Interface name, line protocol Physical status of the interfaces and status of the protocol
Router Id Router ID
Hello Number of seconds until next hello packet is sent out the interface
To display OSPF routing information, use the show ip ospf neighbor command in
Privileged mode.
When executing the show ip ospf neighbor command, the following information about OSPF
neighbors is displayed.
Field Description
Neighbor ID Neighbor ID
Dead Time Waiting time until the router infers that the neighbor is down
To display OSPF route information, use the show ip ospf route command in Privileged
mode.
# show ip ospf route
OSPF process 0:
Codes: C - connected, D - Discard, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
When executing the show ip ospf route command, the following information is displayed.
Low of
Description
Routing Table
3 Area ID
OSPF Commands
Command Description
area
Enable authentication for an OSPF area.
authentication
area default-
Specify a cost for the default summary route sent into a stub or NSSA.
cost
Limit routing information that is transmitted from the specified area to other
area export-list
areas.
area import-list Limit particular routing information that is received from other areas.
area filter-list Filter routes when transmitting route entries using access-list to other protocol.
area range Specify the network range to use summary LSA.
Define the specified area as the stub area not to receive information about the
area stub
external network.
area nssa NSSA is generally used to deliver external routing information to other areas.
area virtual-
Define OSPF virtual links.
link
default-
information Generate a default external route into an OSPF routing domain.
originate
default-metric Set default value for the OSPF routing protocol.
distance Specify administrative distances of OSPF route.
distribute-list Specify the route filtering to be applied when transmitting route entries.
Specify the network that operates OSPF routing protocol, and specify area in
network
which the interface connected to the network is included.
passive- Configure the specified interface not to transmit OSPF routing information to
interface other routers.
redistribute Redistribute routes from other routing domain into OSPF routing domain.
refresh Specify refresh interval of OSPF LSA.
router-id Assign a fixed router ID.
timers spf Change values of the OSPF timers
ip ospf
Assign a password to be used by neighboring routers that are using the OSPF
authentication-
simple password authentication.
key
ip ospf cost Specify cost of OSPF interfaces.
ip ospf Set the interval during which at least one hello packet must be received from a
dead-interval neighbor before the router declare that neighbor down.
ip ospf
Specify the interval between hello packets that are sent on the interface.
hello-interval
ip ospf message-
Specify a ID and a password when enabling OSPF MD5 authentication
digest-key
ip ospf priority Set the router priority, which helps determine the DR for this network.
ip ospf
Specify the time between LSA retransmissions for adjacencies belonging to
retransmit-
the interface.
interval
ip ospf transmit- Set the estimated time required to send a link-state update packet on the
delay interface.
clear ip ospf Clear information learnt from OSPF.
show ip protocols Display information of IP protocol that is operating in the system.
show ip ospf Display basic information of OSPF.
show ip ospf Display the internal OSPF routing table entries to an ABR (Area Border
border-routers Router) and ASBR (Autonomous System Boundary Router).
show ip ospf
Display information about OSPF database of the router.
database
show ip ospf Display OSPF configuration information for interfaces that are defined in the
interface system.
show ip ospf
Display OSPF neighbor information on a per-interface basis.
neighbor
show ip ospf
Display information of OSPF network, routers and external routing tables.
route
Configuring IS-IS
IS-IS Overview
Introduction
IS-IS (Intermediate System to Intermediate System) protocol is the same type of link-state
routing protocol as OSPF. IS-IS can exchange routing information among routers in a particular
domain. IS-IS is defined in RFC 1195 and is usually used for exchanging routing information
among multi-protocol stack such as IP and OSI.
IS-IS network consist of ES (End System) and IS (Intermediate System). ES is an object that
sends and transmits packet as a host. IS is such a router that sends, transmits packets.
IS-IS can be configured to exchange link-state information in limited region because a domain
can be divided to several regions. The limited region is called ‘area’. Routing among areas is
consisted hierarchically, and a domain is divided to small areas and is managed. Level 1 routers
and level 2 routers can be configured for the hierarchical structure. Level 1 routers take charge
of routing in an area. If destination of packets is external area, level 1 routers route packets to
level 2 router. Level 2 router take charge of routing among areas or other domains.
IS-IS protocol selects the shortest path using SPF (Shortest Path First) algorithm. SPF algorithm
calculates status of network interface and path cost that is used in the interface and connected
network, and selects a path that has the lowest cost. SPF algorithm only delivers routing
information when the network is changed. Thus, unnecessary traffic is not delivered. Also, SPF
algorithm can control the complicated and sophisticated network.
Level 1 / Level 2 Router : A router that can be connected to Level 1 routers and Level 2 routers.
- Maintains additional link status for connection of level 1 and level 2.
- Operates the same as an OSPF ABR.
area 49.0001
L1
Level-1
Area
L1 / L2
Level-2
area 49.0002 Backbon area 49.0003
L1 / L2 L1 / L2
Level-1 Level-1
Area Area
L1 L1
IS-IS uses an ISO network address. Each network address plays a role as NSAP (Network
Service Access Point) to distinguish network connection point.
ES can have several NSAP addresses that value of last byte (n-selector) is different. Each NASP
indicates services that can be used on a node. Therefore, ES can have several services, and a
node can be included in several areas.
A IS has specific network address called NET (Network Entity Title). NET is a NSAP address
that last byte (n-selector) is 0x00. Most IS has one NET. However, IS that is configured by
several areas can have several NETs.
49.0001.00a0.c96b.c490. 00
AFI 1 Area ID. The area ID is used for level 1 routing, and each router
Area address Variable (1~12) can define three of area ID.
System ID. The system ID is used for level 2 routing. The system
System ID 6 ID must be unique. The system ID generally uses type of MAC
address.
All routers that are in the same area should use the same area ID.
All nodes that are in the same area should use the same system ID.
System ID length of all nodes that are in the same domain should be the same.
The following types of packets are used in IS-IS for exchanging routing information.
Hello Packet
The Hello packet establishes and maintains relation of adjacent IS-IS systems. There are three
types of hello packet as follows:
Level 1 LAN IS-IS Hello Packet: Used by level 1 routers on a broadcast LAN.
Level 2 LAN IS-IS Hello Packet: Used by level 2 routers on a broadcast LAN.
Point-to-point Hello Packet: Used by medias that do not have broadcasting feature such as a Point-to-
Point link.
Level 1 routers transmit Level 1 LSPs. However, level 2 routers transmit both level 1 LSPs and
level 2 LSPs.
Configuring IS-IS
1. Enabling IS-IS
Enable IS-IS protocol in the Corecess S5 System.
Enable IS-IS
To enable IS-IS protocol in the Corecess S5 System, the following tasks should be executed.
By default, IS-IS is set not to be operated in the Corecess S5 System. To enable IS-IS protocol in
the Corecess S5 System, use the following commands.
Command Description
configure terminal 1. Enter Global configuration mode.
2. Enable IS-IS routing process, and enter IS-IS configuration mode.
router isis <area-tag> Name of IS-IS routing process. <area-tag> is used
[<area-tag>] when configuring several IS-IS area. Also, <area-tag> classify
each area.
net 3. Configuring NET of IS-IS routing process.
<network-entity-title> <network-entity-title> Area address and system ID of IS-
The following example shows how to configure IS-IS protocol and IS-IS NET and how to enable
the IS-IS process in the default VLAN interface.
The following example shows how to set the area tag to classify each process when creating
over two IS-IS process in the system.
Parameter Description
adjacency-check performs consistency checks on hello packets
area-password Set IS-IS area authentication password.
default-information Set default route of IS-IS routing domain to be transmitted to neighbors.
distance Change distance value of IS-IS.
domain-password Set authentication password of IS-IS.
dynamic-hostname Set host name or area tag to be used.
hostname dynamic Set mapping information to be displayed.
ignore-lsp-errors Allow the router to ignore checksum errors of LSP.
is-type Set IS-IS routing level of a router.
lsp-gen-interval Set LSP (Link-State Packet) generation interval.
lsp-refresh-interval Set LSP(Link-state packet) refresh interval.
max-area-addresses Set the maximum number of IS-IS area.
max-lsp-lifetime Set the maximum LSP(Link-state packet) life time.
Specify a passive interface that does not transmit routing information to
passive-interface
other routers.
Apply different values to external route, which is redistributed to IS-IS,
redistribute
depending on types of protocol or the condition of route map.
Set overload bit not to use the local router as an intermediate router in their
set-overload-bit
SPF calculations.
spf-interval Set SPF (Shortest Path First) calculation interval of IS-IS.
summary-address Add the aggregate route entry of IS-IS.
The following example shows how to set the Corecess S5 System to the level 1 (intra-area)
router.
To performs consistency checks on hello packets, use the adjacency-check command in IS-IS
configuration mode.
The following example shows how to configure IPv4 IS-IS router to form an adjacency with
IPv4 or IPv6 routers.
Command Description
lsp-gen-interval level-1 Apply the specified interval to level 1 (intra-area) routing.
[level-1 | level-2] level-2 Apply the specified interval to level 2 (inter-area) routing.
<seconds> <seconds> LSP generation interval (1 ~ 120 seconds)
The following example shows how to IS-IS LSP generation interval to 6 seconds.
Command Description
lsp-refresh- level-1 Apply the specified interval to level 1 (intra-area) routing.
interval [level-1 | level-2 Apply the specified interval to level 2 (inter-area) routing.
level-2] <seconds> <seconds> LSP refresh interval (1 ~ 65535 seconds)
The following example shows how to IS-IS LSP refresh interval to 800 seconds.
To set maximum LSP lifetime, use the following command in IS-IS configuration mode.
Command Description
max-lsp-lifetime
<seconds> maximum LSP lifetime (1 ~ 65535 seconds)
<seconds>
The following example shows how to set maximum LSP lifetime to 1000 seconds.
The following example shows how to ignore LSP that include checksum errors.
Command Description
max-area-addresses
<number> Maximum number of IS-IS static area (3 ~ 254)
<number>
The following example shows how to set the maximum number of IS-IS static area to 10.
Command Description
area-password
<string> Authentication password of IS-IS area
<string>
The following example shows how to set the authentication password to ‘corecess’.
By default, the Corecess S5 System is configured not to transfer a default route. To transfer a
default route to neighbor routers, use the default-information originate command in IS-
IS configuration mode.
The following example shows how to transfer a default route of a IS-IS routing domain
automatically to neighbor routers.
Setting Distance
Distance is a value that is used for comparing routes of different routing protocols that have the
same destination. The default value of the distance is 115 in the Corecess S5 System.
To change the specified IS-IS distance value for topology property or redistribution, use the
distance command in IS-IS configuration mode.
Command Description
distance {level-1 |
level-2} <distance>
level-1 Set distance value of IS-IS level 1 route (intra-area
distance level-1 route).
<distance> level-2 level-2 Set distance value of IS-IS level 2 route (inter-area route).
<distance> <distance> Distance of IS-IS route (1 ~ 255)
distance level-2 <prefix> Prefix of the network in which the router is included or
<distance> level-1 IP address of the router
<distance> <M> Subnet mask of <prefix>
<access-list-number> Number of access list to be applied to
distance <distance> received routing information (500 ~ 999).
[<prefix>/<M>
[<access-list-number>]]
The following example shows how to set IS-IS route distance of the router which is operating on
the network of 198.10.1.0 to 130. The IP address of the router is 198.10.1.3.
(config)# router rip
(config-router)# network 198.10.1.0/32
(config-router)# distance 130 198.10.1.3/32
(config-router)#
Command Description
domain-password
<string> Authentication password of IS-IS routing domain
<string>
The following example shows how to the authentication password of IS-IS routing domain to
‘corecess’.
To use a host name or an area tag for displaying a particular node in IS-IS networks, use the
following command in IS-IS configuration mode.
Command Description
dynamic-hostname
area-tag Use the area tag as the host name.
[area-tag]
The following example shows how to use the host name of a particular node.
The following example shows how to display mapping information for the host name and the
system ID when executing the show isis command.
To specify the passive interface, use the following command in IS-IS configuration mode.
Command Description
loopback id Specify the loopback interface that is used as the
passive interface.
passive-interface
<loopback-id> Loopback interface ID that is set to the passive
{loopback id
interface (1 ~ 32).
<loopback-id>|
port Specify the port that is set to the passive interface.
port <port-type>
<slot>/<port> Slot of the port/Number of the port
gigabitethernet |
vlan Specify the VLAN interface that is set to the passive
vlan id <vlan-id>|
interface.
vlan name <vlan-name>}
<vlan-id> VLAN interface ID (1 ~ 4094)
<vlan-name> VLAN interface name
The following example shows how to specify the VLAN interface as the passive interface.
To set the overload bit, use the following command in IS-IS configuration mode.
Command Description
on-startup <seconds> Set the overload bit only after a system
reload
- <seconds>: Period after the reload during which the overload
set-overload-bit bit is set (5 ~ 86400 seconds)
[on-startup seconds>] suppress Set IP prefix of the specified type not to transmit when
[suppress {external| overload bit is already set.
external Set IP prefix learnt from other protocols not to transmit
interlevel | when overload bit is already set
external interlevel | interlevel Set IP prefix learnt from other IS-IS routing levels not
interlevel external}] to transmit when overload bit is already set.
external interlevel, interlevel external Set IP prefix
learnt from either other protocols or other IS-IS routing levels not to
transmit when overload bit is already set.
To apply different metric values to external route, which is redistributed to IS-IS, depending on
types of protocol or the condition of route map, use the following command in IS-IS
configuration mode.
Command Description
The following example shows how to redistribute RIP routes to IS-IS level 1 routes.
Command Description
<prefix> IP route prefix
<M> Subnet mask of IP route
summary-address level-1 Aggregate routes that are matched to the specified to level 1
<prefix>/<M> [level- routes.
1 | level-1-2 | level-1-2 Aggregate routes that are matched to the specified to
level-2] level 1 and level 2 routes.
level-2 Aggregate routes that are matched to the specified to level 2
routes.
The default SPF calculation interval is 5 seconds. To change the SPF calculation interval, use the
following command in IS-IS configuration mode.
Command Description
The following example shows how to set the SPF calculation interval to 10 seconds.
To display status information of all IS-IS routing processes, use the show isis counter
command in Privileged mode.
isisSysStatSPFRuns: 0
When executing the show isis counter command, the following information is displayed.
Field Description
To display IS-IS routing database information, use the show isis database command in
Privileged mode.
The following example shows how to display the detail information of IS-IS routing database
using the show isis database detail command.
Field Description
LSPID LSP ID. The first six octets form the system ID of the router that originated the LSP.
LSP sequence number. This LSP sequence number is increased whenever LSP is
LSP Seq Num
updated.
LSP Checksum Checksum of all LSP packets.
Amount of time the LSP remains valid (in seconds). If this value becomes zero, the
LSP Holdtime
LSP is removed from LSDB of all routers.
Attach bit. If this value is 1, it means that the router is connected to at least one area
ATT
through level 2 router.
P P bit. If this value is 1, it means that the router provides area partition-repair feature.
Overload bit. If this value is 1, it means the router is overloaded. Therefore, other
OL
routers cannot use the router as an intermediate router when SFP calculation.
Area Address Area address that the router can reach.
NLPID NLP(Network Layer Protocol) ID
IP Address IP address of the interface
Metric IS-IS metric value and IP prefix/subnet mask of the interface
To display IS-IS routing process information of all interfaces, use the show isis interface
Field Description
Routing protocol Routing Protocol that is operating on the interface (area tag)
To display the list of routers that are connected to IS area, use the show isis topology
command in Privileged mode.
Area corecess:
IS-IS paths to level-1 routers
System Id Metric Next-Hop Interface SNPA
0000.0000.0020 --
0000.0000.000a 10 0000.0000.000a vlan1 00e0.b064.46ec
IS-IS paths to level-2 routers
System Id Metric Next-Hop Interface SNPA
0000.0000.0020 --
0000.0000.000a 10 0000.0000.000a vlan1 00e0.b064.46ec
0000.0000.000b 20 0000.0000.000b vlan1 00e0.b064.46ec
#
When executing the show isis topology command, the following information is
displayed.
Field Description
IS-IS Commands
The following IS-IS commands are provided in the Corecess S5 System.
Command Description
adjacency-check Perform consistency checks on hello packets.
area-password Set the IS-IS area authentication password.
Reset IS-IS (Intermediate System-to-Intermediate System) configuration
clear isis
information.
distance Specify administrative distance value of IS-IS routes.
domain-password Set authentication password of a IS-IS routing domain.
Set a host name or an area tag to be used for displaying a particular node in
dynamic-hostname
IS-IS networks.
Display mapping information for a host name and a system ID when
hostname dynamic
executing the show isis command.
ignore-lsp-errors Allow the router to ignore checksum errors of LSP.
ip router isis Enable IS-IS routing protocol on the interface.
is-type Set IS-IS routing level of the router.
isis circuit-type Set IS-IS routing level on the specified interface.
isis csnp-interval Set IS-IS CSNP (Complete Sequence Number PDUs) transmission interval.
isis hello padding Enable the padding function.
isis hello-
Set transmission interval of IS-IS hello packets on the specified interface.
interval
isis Specify multiplier value that is used when calculating transmission interval
hello-multiplier of IS-IS hello packets.
isis lsp-interval Set transmission interval of IS-IS LSPs.
isis mesh-group Set the specified interface to a member of the specified mesh group.
isis metric Specify the metric value of the specified interface.
isis password Set IS-IS authentication password of the specified interface.
isis priority Set priority of the DR (Designated Router).
isis
retransmit- Set retransmission interval of IS-IS LSPs (Link-state packet).
interval
max-area-addresses Set the maximum number of IS-IS areas that can be configured as static area.
Set maximum LSP lifetime that IS-IS LSP(Link-state packet) persist without
max-lsp-lifetime
being refreshed.
net Configure NET of the IS-IS routing process
Specify a passive interface that does not transmit routing information to
passive-interface
other routers.
Apply different values to external route, which is redistributed to IS-IS,
redistribute
depending on types of protocol or the condition of route map.
Redistribute IS-IS level 1 routes to level 2 routes, or redistribute level 2
redistribute isis
routes to level 1 routes.
router isis Enable IS-IS routing protocol, and enter IS-IS routing configuration mode.
Set overload bit not to use the local router as an intermediate router in their
set-overload-bit
SPF calculations.
spf-interval Set SPF (Shortest Path First) calculation interval of IS-IS.
summary-address Add the aggregate route entry of IS-IS.
Configuration RIP
RIP (Routing Information Protocol) Overview
Introduction
RIP (Routing Information Protocol) is a dynamic routing protocol that exchange routing
information in internal AS (Autonomous System). RIP is used for small-scale networks.
Dynamic routing protocol exchanges messages with routers and applies changed network
status to routing tables when a topology is changed, or an error occurs. RIP transmits its routing
information (RIP message) periodically to all of connected neighbor routers through number
520 of UDP port. And, RIP receives routing information from neighbor routers and modifies its
routing table. When routing information is advertised as above, all router of internal AS can
exchange their routing information.
If there are several routes that have the same destination in the routing table, RIP selects the
shortest path using the distance-vector algorithm. The distance-vector algorithm selects the
shortest next hop and the shortest distance (or cost) of the destination as the best path. A
routing protocol can be easily configured using the algorithm, and less system memory is used.
The distance of each path is called metric in RIP. The network administrator can specify the
metric depending on path state or speed. The default metric value is 1. RIP selects the path that
has the lowest value of metrics as the best path. Therefore, the metric is the basic value to select
paths in RIP.
The disadvantage of RIP is the occurrence of a routing loop. The routing loop occurs when
routers consider that the routers can reach the destination through each other and exchange
routing information continuously. To prevent this situation, RIP limits metric value to less than
15. If there is a path that metric value is over 15, RIP considers the path unreachable, and the
path cannot be transmitted to neighbors. For this reason, RIP is generally used in single AS
(Autonomous System). Split Horizon or triggered update is used to solve the routing loop.
RIP Version
The Corecess S5 System supports RIP version 1 (RIPv1) and RIP version 2 (RIPv2). The
difference of two versions is as follows:
By default, RIPv2 is operated in the Corecess S5 System. RIPv1 does not support subnet mask.
Thus, RIPv2 is recommended.
Each route entry in RIP routing table consist of the following fields.
Field Description
Destination IP address and subnet mask of destination
Next hop The IP address of neighbor router to reach the destination.
Route change flag Flag for indicating the recent change of the route entry
Timer The last time the route was updated
RIP Operation
RIP Timer
RIP uses numerous timers to regulate its performance. These include a routing-update timer, a
route-timeout timer, and a route-flush timer.
Timer Description
Interval between periodic routing updates. Generally, it is set to 30 seconds, with a small
Update random amount of time added whenever the timer is reset. This is done to help prevent
Timer congestion, which could result from all routers simultaneously attempting to update
their neighbors.
Interval in seconds during which routing information regarding better paths is suppressed.
It should be at least three times the value of update. A route enters into a holddown state
Holddown when an update packet is received that indicates the route is unreachable. The route is
Timer marked inaccessible and advertised as unreachable. However, the route is still used for
forwarding packets. When holddown expires, routes advertised by other sources are
accepted and the route is no longer inaccessible. The default is 180 seconds.
Amount of time in seconds that must pass before the route is removed from the routing
Flush table; the interval specified should be greater than the invalid value. If it is less than this
Timer sum, the proper holddown interval cannot elapse, which results in a new route being
accepted before the holddown interval expires. The default is 240 seconds.
The Split Horizon and the Triggered Update prevent the routing loop.
10.1.1.0
For example, the router A is connected to the network of 10.1.1.0 as above. The router B is
connected to the network of 10.1.1.0 through the router A, and the router C is connected to the
network of 10.1.1.0 through the router A and the router B.
Let’s assume that the link between the router A and the network of 10.1.1.0 is disconnected.
When the router A detects link disconnection, the router A removes this route entry from its
routing table. But, the router B does not realize the link disconnection and sends its routing
table to the router A using the update message. The router A finds the route entry of 10.1.1.0
from the received routing entry and increases metric value of the route entry, then adds the
route entry into its routing table. After that, the router B also receives the route entry of 10.1.1.0
from the router C and increases the metric value of the route entry, then adds the route entry
into its routing table. The router B sends its routing entry to the router A. If this situation is
continued, although the routers cannot actually reach to the network of 10.1.1.0, the routers
increase the metric values and update their routing table. Finally, the entry of 10.1.1.0 becomes
the invalid route when the metric value is 16, and the network becomes unreachable destination.
The above situation is called routing loop, and the routing loop is solved when the metric value
of route entry is 16. There are two solutions to solve the routing loop.
First solution is that the router does not allow information, which is transmitted by itself, to be
transmitted to other routers. If this solution is used in the above network, because network
information of 10.1.1.0 is transmitted through the router A to the router B, the router B transmits
the rest information to router A except the route entry of 10.1.1.0 network. This solution is
called split horizon. Split horizon with poisoned reverse, which is similar to split horizon, sets
the metric value to 16 instead of removing the entry.
Second solution, triggered update, is that the router transmits changed information
immediately to other routers when the router receives new routing information or detects
change of existing routing information by a physical cause. If this solution is used in the above
network, when the router A detects the link disconnection, the router informs the router B
immediately that the network of 10.1.1.0 is unreachable.
Configuring RIP
1. Enabling RIP
Enable RIP in the Corecess S5 System.
Enable RIP
By default, RIP is disabled in the Corecess S5 System. To enable RIP, use the router rip
command in Configure configuration mode.
# configure terminal
(config)# router rip
(config-router)#
After enabling RIP in the Corecess S5 System, specify network in that RIP is operated. To
operate RIP on the specified network, use the network command in RIP configuration mode.
Command Description
<network-address> IP address of the network of directly
network
connected networks.
<network-address>/<M>
<M> Subnet mask of network
The Corecess S5 System can only exchange RIP update messages with neighbor routers through
interfaces of the network that is specified using the network command.
The following example shows how to enable RIP on the network of 128.9.0.0/24 and
192.31.7.0/24.
Parameter Description
Distance Specify administrative distance value of the RIP route.
Specify default metric values that are applied when redistributing all routing
Default metric
entries to RIP networks.
Set the specified interface not to transmit RIP routing information to other
Passive Interface
routers.
Distribute list Filter routes that are matched with condition of the specified access list
Change metric values of RIP route entries that are matched with condition of the
Offset list
specified access list.
Timer Specify RIP timer (update, holddown, flush) values.
RIP version Specify RIP protocol version.
Setting Distance
Distance is a value that is used for comparing routes of different routing protocols that have the
same destination. The default value of the distance is 120 in the Corecess S5 System.
Lower distance value is higher priority. To change the specified RIP distance value for topology
property or redistribution, use the distance command in RIP configuration mode.
Command Description
<distance> Distance of RIP route (1 ~ 255)
distance <distance> <ip-address> IP address of the network or router
[<ip-address>/<M> <M> Subnet mask
[<access-list-number>]] <access-list-number> Access list number to apply to the
received routing information (500 ~ 999)
The following example shows how to set the RIP route distance of 192.16.10.3 to 100 on the
network of 192.16.10.0.
To specify the passive interface, use the passive-interface command in RIP configuration
mode.
Command Description
loopback id Specify the loopback interface that is used as the
passive-interface
passive interface.
{loopback id
<loopback-id> Loopback interface ID that is set to the passive
<loopback-id>|
interface (1 ~ 32).
port gigabitethernet
port Specify the port that is set to the passive interface.
<slot>/<port>|
<slot>/<port> Slot of the port/Number of the port
vlan id <vlan-id>|
vlan Specify the VLAN interface that is set to the passive interface.
vlan name
<vlan-id> VLAN interface ID (1 ~ 4094)
<vlan-name>}
<vlan-name> VLAN interface name
The following example shows how to specify the 1/1 port as the passive interface.
When external routes are distributed to RIP, metric values of external router are change to other
values that can be used in RIP network. It is because concept of metric is different between RIP
and other protocols.
There are two methods to change metric values of external routers to metric values of RIP
network.
Apply different metric values without types of routing protocols or condition of route map
To specify the default metric, use the default-metric command in RIP configuration mode.
Command Description
default-metric <number> <number> default metric value (0 ~ 16)
The following example shows how to set the default metric value of RIP to 10:
(config-router)# default-metric 10
(config-router)#
Apply different metric values without types of routing protocols or condition of route
map
In the Corecess S5 System, different metric values can be applied to external route entries from
other types of routing protocol when redistributing external entries to RIP networks.
To apply different values to external routes that are redistributed depending on types of routing
protocol or condition of route map, use the redistribute command in RIP configuration mode.
Command Description
redistribute <protocol>
<protocol> Type of route to redistribute
[metric <metric>]
<metric> Cost of the route entry (1 ~ 16)
[route-map <route-map-
<route-map-name> Name of route map
name>]
In the following network, if you set each router (RTA, RTB, RTC) of the RIP network to receive
routing information from OSPF network, use the following commands.
Filtering Route
To filter routes that are matched with particular condition of access list, use the distribute-
list command in RIP configuration mode.
Command Description
distribute-list <access-list-num> Number of the access list to apply (500 ~ 999)
<access-list-num> in Filter route that are matched with the specified condition of access
{in | out} {port list when receiving routing information.
gigabitethernet out Filter route that are matched with the specified condition of access
<slot>/<port>| list when transmitting routing information.
vlan id <vlan-id>| <slot>/<port> slot number/port number
vlan name <vlan-id> VLAN interface ID to apply access list (1 ~ 4094)
<vlan-name>} <vlan-name> VLAN interface name to apply access list
The following example shows how to filter routes that are matched with condition of access list
500 in routing information from which port 5/1 of the system receives.
The following example shows how to filter routes that are matched with condition of access list
500 in routing information to which port 5/1 of the system transmits.
To define an offset list, use the offset-list command in RIP configuration mode.
Command Description
offset-list <access-list-num> Access list number to apply (500 ~ 999).
<access-list-num> in Applies the access list to incoming metrics.
{in | out} <offset> out Applies the access list to outgoing metrics.
[port gigabitethernet <offset> Positive offset to be applied to metrics for networks
<slot>/<port>| matching the access list. If the offset is 0, no action is taken.
vlan id <vlan-id>| <slot>/<port> Slot number/port number of the port.
vlan name <vlan-id> Id of the VLAN to which the offset-list is applied.
The following example shows how to add 10 to metric value of route entries that are matched
with condition of access list 21 when transmitting routing information through all interfaces.
# configure terminal
(config)# router rip
(config-router)# offset-list 21 out 10
The following example shows how to add 5 to metric value of route entries that are matched
with condition of access list 22 when receiving routing information from port 5/1 of the system.
# configure terminal
(config)# router rip
(config-router)# offset-list 22 in 5 vlan id 51
Setting Timer
Routing protocols use several timers that determine such variables as the frequency of routing
updates, the length of time before a route becomes invalid, and other parameters. You can
adjust these timers to tune routing protocol performance to better suit your internetwork needs.
You can make the following timer adjustments:
To change values of RIP timers, use the timers basic command in RIP configuration mode.
Command Description
# configure terminal
(config)# router rip
(config-router)# timers basic 30 100 50
To change RIP version of all interfaces that are defined in the router, use the version
command in RIP configuration mode.
Command Description
# configure terminal
(config)# router rip
(config-router)# version 1
(config-router)#
RIP ECMP Routing supports multiple equal-cost paths between routers, and distributes the
traffics among the possible paths. Maximum 4 links can working with one ECMP link and the
traffic can be shared on a basis of IP address destination session.
The following example show how RIP routers execute load balancing by the Equal Cost
Multipath Routing Protocol.
To display RIP routing tables, use the show ip rip command in Privileged mode.
# show ip rip
Codes: R - RIP, C - connected, O - OSPF, B - BGP, S - static
(n) - normal, (s) - static, (d) - default, (r) - redistribute,
(i) - interface
When executing the show ip rip command, the following information is displayed.
Field Description
Entry code, destination network address or host ip address / bit number of subnet mask
Types of entry code are as follows:
Network
R : RIP Entry C : Connected Entry
O : OSPF Entry B : BGP S : Static Entry
IP address of the next system that is used when forwarding a packet to the destination
Next
network. If the router connects directly to the destination, ‘0.0.0.0’ is displayed.
Remain time to remove the path. Holddown timer value is displayed for the first time.
Time Then, after holddown timer value becomes zero, flush timer value is displayed. After even
flush timer value becomes zero, the path is removed from the routing table.
To display RIP configuration information for all interfaces that are defined in the system, use
the show ip rip interface command in Privileged mode.
When executing the show ip rip interface command, the following information is
displayed.
Field Description
To display the current RIP version, use the show ip protocols command in Privileged
mode.
# show ip protocols
RIP Commands
Command Description
default-
Allow the router to advertise RIP default route information to neighbor
information
routers
originate
Specify default metric values that are applied when redistributing all routing
default-metric
entries to RIP networks.
distance Specify administrative distance value of the RIP route.
distribute-list Filter routes that are matched with condition of the specified access list
network Specify the network to operate RIP routing protocol.
Change metric values of RIP route entries that are matched with condition of
offset-list
the specified access list.
Set the specified interface not to transmit RIP routing information to other
passive-interface
routers.
Redistribute routing information of other routing protocols to routing
redistribute
information of RIP network.
route Add a RIP static route.
timers basic Specify RIP timer (update, holddown, flush) values.
version Specify RIP protocol version.
ip rip
authentication key- Enable authentication process for RIPv2, and define keys for interfaces.
chain
ip rip
authentication Specify authentication method for RIPv2 packets.
mode
ip rip authentic-
Specify authentication string for RIPv2 packets.
cation string
ip rip receive Specify RIP version of packets from which the interface receives.
version
ip rip send
Specify RIP version of packets to which the interface transmits.
version
clear ip rip Reset information that is learnt from RIP.
Configuration for the purpose of load balancing for the traffic with Equal Cost
equal-cost-multipath
Multipath Routing
show ip protocols Display IP protocol information that is operating in the system.
show ip rip Display the contents of RIP routing table.
show ip rip Display RIP configuration information for all interfaces that are defined in
interface the system.
This chapter describes how to configure a trunking group by using LACP (Link Aggregation Control
Protocol).
Port Trunking Overview
For example, the maximum bandwidth of the port that connects the system A and the system B
is 1Gbps, but the amount of data that receives and transmits between two systems can exceed
1Gbps. Port trunking can be used in the case. Several ports act as single port, so it can be easily
managed by VLAN, STP and IGMP. Port trunking also effects stability of the system. Even if
some ports that are included in a trunking group are not operating normally, communication
can be continued by rest ports.
In the System, port trunking can be implemented by 802.ad link aggregation, and 802.3ad link
aggregation uses LACP (Link Aggregation Control Protocol). LACP allows ports that have the
same link aggregation key value to configure themselves into a trunking group.
If you do not use STP, you should complete port trunking configuration to prevent loops
before connecting network cables between systems.
All trunk group members (ports) should have the same media type (10/100Base-T, 100FX, or
Gigabit)
All trunk group members (ports) should be set to the same port speed, duplex mode, and
operation mode.
All trunk group members (ports) should be set to the full-duplex mode.
If LACP operation mode is set to active on a port that is located in the end of a trunk, trunk is
set automatically.
When a QoS trunk is specified, the aggregated ID of the trunk group is used. The aggregated ID
is decided by the following rules.
For example, if 1/1, 1/2, 1/3 and 1/4 ports aggregates, the lowest port (1/1) is decided to the
aggregated ID.
LACP Key
LACP key is used to identify the trunk in which the port is included. All ports that are in the
single trunk have the same key value.
Passive mode
When you enable a port for passive link aggregation, the System port can exchange
LACPDU messages with the port at the remote end of the link, but the System port cannot
search for a link aggregation port or initiate negotiation of an aggregate link. Thus, the port
at the remote end of the link must initiate the LACPDU exchange.
Manual mode
When you enable a port for manual link aggregation, you can manually configure aggregate
links containing multiple ports
To configuring a dynamic LACP trunk, one end of ports should be configured to LACP active
mode and the other end of ports should be configured to LACP active or LACP passive mode.
Switch A Switch B
To configure a trunk manually, both ends of the ports should be configured to LACP manual
mode.
Switch A Switch B
To assign the LACP key and set LACP operation mode, use the following commands:
Command Description
configure terminal 1. Enter Global configuration mode.
2. Assign LACP key and specify the LACP operation mode for the
specific ports.
<key-num> LACP key value(1 ~ 65535)
lacp key <key-num> <slot>/<port> Slot/Port number
port gigabitethernet active Enable active mode. Aggregation link is created, channels
<slot>/<port> mode are initialized in active mode. If the remote LACP mode is active of
{active | passive | passive, aggregation link is created.
manual} passive Enable passive mode. Channels are not initialized in
passive mode, but LACP packets can be processed.
manual Enable manual mode. Aggregation link can be
configured without LACP in manual mode.
lacp : Change LACP parameter
actor-timeout : LACP_timeout
short : short
lacp actor-timeout
long : long
(short|long) port port
fastethernet : FastEthernet port type
type WORD
gigabitethernet : GigabitEthernet port type
epon : Ethernet PON port type
tengigabitethernet : 10G Ethernet port type
# configure terminal
(config)# lacp key 10 port gigabitethernet 1/3 mode active
(config)# end
# show lacp port gigabitethernet 1/3
System A
Trunk Group
Port : 5/1-4 on System A
5/1-4 on System B
LACP admin key : 33
System B
System A
The following shows how to configure the LACP trunk on the System A:
System B
The following shows how to configure the LACP trunk on the System B:
When a packet is L2 switched or L3 routed to a trunk group, the actual port selection is made
based on one of six criteria:
Filed Description
In all cases, three bit(the LSBs) are used to index into a trunk table to choose one of eight
possible ports. SIP and DIP criteria are used for Ipv4 packets; for other packets the selection falls
back to criteria based on the equivalent MAC address.
Broadcast, Multicast, and DLF packets are sent to a single port in a trunk group. Several
registers are provided to control which port is used for each type of traffic. A mechanism is
provided to control distribution of unknown multicast packets over trunk ports. This is
accomplished by using the FFP to filter on a destination port = 0x1d and the least significant 3
bits of the Destination MAC address. Then set up 8 corresponding IRULES with ACTION bit 16
set and use the CLASSIFICATION_TAG field to indicate which trunk ports are allowed to
receive the packet. THE CLASSIFICATION_TAG is ANDed with the port bitmap is this
scenario.
all : All
ip : Ip Only
Introduction
A network that has several paths for one destination is fault-tolerant. It is because packets can
be transmitted through other paths even if one of paths cannot be used on the network. But,
loops might occur on the network. If a loop is occurs between two nodes, when packets are
broadcasted, the packet transmission is repeated infinitely. Because of the loop, the network can
be congested, then the network becomes instable.
In the following network configuration, there are two paths from Switch A to Switch C. One of
the path is path 2 connected directly and the other path is path 1 and path 2 through Switch B.
A loop is formed in this network because multiple active paths exist between Switch A and
Switch C. In this network, end stations might receive duplicate messages. For example, if Switch
A broadcasts packets, Switch C broadcasts the received packets to Switch A, and Switch A
broadcast the packets again.
Switch A
Path 1 Path 2
Path 3
Switch B Switch C
STP (Spanning Tree Protocol) prevents the loop on the network in which several paths are
existed. STP defines a tree with a root switch. When two interfaces on a switch are part of a loop,
the spanning-tree port priority and path cost settings determine which interface is put in the
forwarding state and which is put in the blocking state. Spanning tree forces redundant data
paths into a standby (blocked) state. Therefore, when traffic is processed, packets are only
transmitted through paths of non-blocking state.
If the path 3 is blocked in the network configuration mentioned previously, you can have a
loop-free path between Switch A and Switch C as follows:
Switch A
Path 2
(Forwarding)
Path 1
(Forwarding)
Path 3
Switch B (Blocking) Switch C
Switches send and receive spanning-tree frames, called bridge protocol data units (BPDUs), at
regular intervals. The switches do not forward these frames, but use the frames to construct a
loop-free path.
If a network segment in the spanning tree fails and a redundant path exists, the spanning-tree
algorithm recalculates the spanning-tree topology and activates the standby path.
Root Switch
Designated Designated
Switch Switch
Designated Port
Designated
Switch
When the switches in a network are powered up, each function operates as the root switch.
Each switch sends a configuration BPDU through all of its ports. The BPDUs communicate and
compute the spanning-tree topology. Each configuration BPDU contains this information:
- Unique bridge ID of the switch that the sending switch identifies as the root switch
- Spanning-tree path cost to the root
- Bridge ID of the sending switch
- Aging time of BPDU
- Interface ID that transmits BPDU
- Spanning tree timer values (Hello, Forward delay, Max-age)
Bridge ID determines the selection of the root switch. Each VLAN on the switch has a unique 8-
byte bridge ID; the two most-significant bytes are used for the switch priority, and the
remaining six bytes are derived from the switch MAC address. The switch with the highest
switch priority (the lowest numerical priority value) is elected as the root switch. If all switches
are configured with the default priority (32768), the switch with the lowest MAC address in the
VLAN becomes the root switch.
Path cost determines the selection of the root port and designated switch. The port that provides
the best path (lowest cost) when the switch forwards packets to the root switch is called the root
port. The switch that provides the lowest path cost when forwarding packets from that LAN to
the root switch is called the designated switch. The port through which the designated switch is
attached to the LAN is called the designated port.
A root port is selected for each switch (except the root switch). This port provides the best path
(lowest cost) when the switch forwards packets to the root switch.
BPDU has three spanning-tree timers (hello, forward delay, max age). The following table
describes the timers that affect the entire spanning-tree performance:
Timer Description
When this timer expires, the interface sends out a Hello message to the neighboring
Hello timer
nodes.
Forward delay Determines how long each of the listening and learning states last before the
timer interface begins forwarding.
Determines the amount of time the switch stores protocol information received on an
Max age timer
interface.
Blocking State
BPDU Transmission
Learning State
Forward delay
Forwarding State
A port that STP is operating always starts at the blocking state. When a switch is initialized, the
switch assumes that the switch is the root switch and transmits BPDU to connected devices
through all ports. Ports of the blocking state discards all frames except BPDU. Ports that receive
BPDU become the listening state.
Ports of the listening state exchange BPDUs with other devices and select the root switch. Then,
after forward delay time is passed, the listening state becomes the learning state.
Ports of the learning state learn MAC addresses to transmit frames. Then, after forward delay
time is passed, the learning state becomes the forwarding state. Frames that are received before
ports become the forwarding state are discarded. After the forwarding, received frames are
transmitted through ports.
Ports of the disabled state do not participate in the spanning tree. These ports neither transmit
or receive BPDUs and do not transmit frames.
Selecting Path
The STP uses a spanning-tree algorithm to select one switch of a redundantly connected
network as the root of the spanning tree. The algorithm calculates the best loop-free path
through a switched Layer 2 network by assigning a role to each port based on the role of the
port in the active topology.
When two interfaces on a switch are part of a loop, the spanning-tree port priority and path cost
settings determine which interface is put in the forwarding state and which is put in the
blocking state. The port priority value represents the location of an interface in the network
topology and how well it is located to pass traffic. The path cost value represents media speed.
Spanning tree forces redundant data paths into a standby (blocked) state. If a network segment
in the spanning tree fails and a redundant path exists, the spanning-tree algorithm recalculates
the spanning-tree topology and activates the standby path.
The key difference between STP and RSTP is the transition states of a port. STP moves a port
from the blocking state to the forwarding state after the listening and the learning state. RSTP
reduces the transition steps by moving directly a port from the blocking state to the forwarding
state. This allows rapid reconfiguration capability when the topology has changed.
10Mbps 2,000,000
10Gbps 2,000
Configuring STP
This section describes how to configure spanning-tree features on the System.
Setting spanning tree timers (Hello time, Max age, Forward delay)
Command Description
configure terminal 1. Enter Global configuration mode.
2. Enable STP on the specified Port VLAN.
stp vlan id <vlan-id>
<vlan-id> Port VLAN ID (1 ~ 4094)
stp protocol-version
3. Set spanning tree protocol to STP.
stp vlan id <vlan-
<vlan-id> Port VLAN ID (1 ~ 4094)
id>
end 4. Enter Privileged mode.
show stp vlan {all |
5. Verify STP configuration.
id <vlan-id>}
# configure terminal
(config)# stp vlan id 1
(config)# stp protocol-version stp vlan id 1
(config)# end
# show stp vlan id 1
VLAN ID: 1
Protocol Operation: enabled
STP version: stpCompatible(0)
Pathcost Encoding: 32bit
BridgeID: 0x8000-0001020000DB
Time since topology change: 1539(s)
.
.
.
#
Disable STP only if you are sure there are no loops in the network topology . When STP is
disabled and loops are present in the topology, excessive traffic and indefinite packet
duplication can drastically reduce network performance. To disable STP on a Port VLAN basis,
enter the no stp vlan command in Global configuration mode. The following example
shows how to disable STP on the Port VLAN whose ID is 1:
If you disable STP on a VLAN, STP is disabled on all ports belongs to the VLAN.
The following example enables STP on the port 1/3 and 1/4:
To disable STP on a specific port, enter the no port command in Global configuration mode.
The following example disables STP on the Gigabit Ethernet port 1/3 ~ 1/4:
To change the bridge priority of a Port VLAN, use the following commands.
Command Description
configure terminal 1. Enter Global configuration mode.
The following example shows how to set bridge ID for a Port VLAN to 3000 (hexa-decimal :
0x0BB8):
# configure terminal
(config)# stp bridge-priority 3000 vlan id 2
(config)# end
# show stp vlan id 2
VLAN ID: 2
Protocol Operation: enabled
Root Bridge: yes
STP version: rstp(2)
Pathcost Encoding: 32bit
BridgeID: 0x0BB8( 3000)-0001AB0DEF11
Time since topology change: 16(s)
Topology changes: 2
Designated Root BridgeID: 0x8000(32768)-0001AB0DEF11
Root Path Cost: 0
.
.
#
To restore the bridge priority for a Port VLAN to the default priority (32768, hexa decimal :
0x8000), enter the no stp bridge-priority command.
VLAN ID: 2
Protocol Operation: enabled
Root Bridge: yes
STP version: rstp(2)
Pathcost Encoding: 32bit
BridgeID: 0x8000(32768)-0090A3000004
Time since topology change: 7363(s)
Topology changes: 0
.
.
.
#
If you want to rarely use a port that is high speed because of a lack of stability or other reasons,
you specify high path cost of the port.
To configure the path cost for the specified port, use the following commands.
Command Description
configure terminal 1. Enter Global configuration mode.
port <port-type> 2. Set the path cost for a specific port..
gigabitethernet <slot>/<port> slot/port number of a port
The following example shows how to set the path cost for the Gigabit Ethernet port 1/3 to 10:
Link State: up
Protocol Operation: enabled
Pathcost Encoding: 32bit
Port State: forwarding(5)
Port Role: RootPort
Mother BridgeID: 0x8000-0090A3000003
Port Number(logical): 129
Port Priority: 0x8
Designated Root BridgeID: 0x8000-004455CCDD00
Designated Path Cost: 10
Designated BridgeID: 0x8000-0090A3040000
Designated PortID: 0x8018
AdminEdge: false
OperEdge: false
AdminPointToPoint: auto(2)
OperPointToPoint: true
#
Recommendation: We recommend that you set the path cost as follows according to the
running STP protocol version and the media speed of the port:
Command Description
stp pathcost-encoding
2. Configure the type of STP encoding mode.
stp8021d1998
The following example shows how to configure the type of STP encoding mode to 16 bits:
VLAN ID: 1
Protocol Operation: enabled
Root Bridge: yes
STP version: rstp(2)
Pathcost Encoding: 16bit
BridgeID: 0x8000-0090A3000003
.
.
#
Command Description
The following example shows how to configure the port priority of the Gigabit Ethernet port
1/3 to ‘1’:
Link State: up
Protocol Operation: enabled
Pathcost Encoding: 32bit
Port State: forwarding(5)
Port Role: RootPort
Mother BridgeID: 0x8000-0090A3000003
Port Number(logical): 129
Port Priority: 0x1
Designated Root BridgeID: 0x8000-004455CCDD00
Designated Path Cost: 200000
Designated BridgeID: 0x8000-0090A3040000
.
.
You can set spanning tree timers for individual Port VLANs. To set STP timers for a specified
Port VLAN, use the following commands.
Command Description
The following example shows how to set spanning tree timers for a Port VLAN:
VLAN ID: 2
Protocol Operation: enabled
Root Bridge: yes
STP version: rstp(2)
Pathcost Encoding: 32bit
BridgeID: 0x8000-0001AB0DEF11
To return the STP hello timer value to the default value, use the no stp hello-time
command in Global configuration mode.
The following example shows how to set the STP forward delay timer to 20 seconds for the
Port VLAN that ID is 2.
VLAN ID: 2
Protocol Operation: enabled
Root Bridge: yes
.
.
ForwardDelay: 15(s)
Bridge MaxAge: 20(s)
Bridge HelloTime: 5(s)
Bridge ForwardDelay: 20(s)
.
.
#
To return the STP forward delay timer value to the default value, use the no stp forward-
time command in Global configuration mode.
The following example shows how to set the STP max age timer to 30 seconds for the specified
Port VLAN that ID is 2.
VLAN ID: 2
Protocol Operation: enabled
Root Bridge: yes
STP version: rstp(2)
Pathcost Encoding: 32bit
BridgeID: 0x8000-0001AB0DEF11
Time since topology change: 106(s)
Topology changes: 2
Designated Root BridgeID: 0x8000-0001AB0DEF11
Root Path Cost: 0
Root Port Number(logical): 0
MaxAge: 20(s)
HelloTime: 2(s)
ForwardDelay: 15(s)
Bridge MaxAge: 30(s)
Bridge HelloTime: 5(s)
Bridge ForwardDelay: 20(s)
.
.
#
To return STP max age timer value to the default value, use the no stp max-age command in
Global configuration mode.
Configure RSTP
This section describes how to configure RSTP on the System.
To set spanning tree protocol to STP on a particular VLAN, use the following commands.
Command Description
stp protocol-version
2. Set spanning tree protocol to STP on the specified VALN.
rstp vlan id <vlan-
<vlan-id> VLAN ID (1 ~ 4094)
id>
The following example shows how to set spanning tree protocol to STP on the Port VLAN
whose ID is 1:
Note: RSTP is automatically compatible with STP. The equipment in which RSTP is operating
sends STP BPDU instead of RSTP BPDU afterwards once the STP BPDU is received from a
connected device. Therefore, it isn’t necessary to execute the stp protocol-version stp
command in case RSTP is activated at VLAN.
20만으로 정정
Gigabit Ethernet link (1Gbps): 20,000
If you want to rarely use a port that is high speed because of a lack of stability or other reasons,
you specify high path cost of the port.
To configure the path cost for the specified port, use the following commands.
Command Description
The following example shows how to set the path cost for the Gigabit Ethernet port 1/3 to 20000:
Link State: up
Protocol Operation: enabled
Pathcost Encoding: 32bit
Port State: forwarding(5)
Port Role: RootPort
Mother BridgeID: 0x8000-0090A3000003
Port Number(logical): 129
Port Priority: 0x8
Recommendation: We recommend that you set the path cost as follows according to the
running RSTP protocol version and the media speed of the port:
To change path cost of 16 bits to path cost of 32 bits again, use the following commands.
Command Description
stp pathcost-encoding
2. Configure the type of RSTP encoding mode.
stp8021t2001
The following example shows how to configure the type of STP encoding mode to 32 bits:
Edge ports assume designated port roles. Port flapping does not cause any topology change
events on Edge ports since RSTP does not consider Edge ports in the spanning tree calculations.
However, if any incoming BPDU is received from a previously configured Edge port, RSTP
automatically makes the port as a non-edge port. This is extremely important to ensure a loop
free Layer 2 operation since a non-edge port is part of the active RSTP topology.
Command Description
The following example shows how to configure the Gigabit Ethernet port 1/3 as an Edge port:
B0DEF11
Designated Path Cost: 200000
Designated BridgeID: 0x8000-0001AB0DEF11
Designated PortID: 0x8001
AdminEdge: true
OperEdge: true
AdminPointToPoint: auto(2)
OperPointToPoint: true
.
.
#
Configuring Self-loop-detection
Table 15-15 Configuring STP self-loop-detection
Command Description
port pathcost Sets the spanning-tree port path cost for the specified port.
port priority Sets the spanning-tree port priority for the specified port.
Enables or disables STP(Spanning Tree Protocol) on the specified
port stp
Ethernet port.
show stp port Displays spanning-tree information for the specified port.
Displays spanning-tree information for the specified VLAN
show stp vlan
interface.
port gigabitethernet 1/3
Configures a port as an Edge port.
bridge-edge-assumption 메모 [zwyi9]: 수정
stp bridge-priority Sets the bridge ID for a VLAN.
stp forward-delay Sets the bridge forward delay for a VLAN.
stp hello-time Sets the bridge hello time for a VLAN.
stp max-age Sets the bridge maximum aging time for a VLAN.
stp pathcost-encoding Configures the type of Spanning Tree Protocol encoding mode.
Configure the type of Spanning Tree Protocol mode to run for a
stp protocol-version
specific VLAN.
stp vlan Enables the spanning tree algorithm for a specific VLAN.
stp self-loop-detection Sets the self-loop-detection for a VLAN.
MSTP
MST Region A CST Root Switch MST Region B
IST IST
This Chapter describes how to configure VRRP (Virtual Router Redundancy Protocol) on the Corecess S5
System.
Configuring VRRP
Configuring VRRP
This section overviews VRRP (Virtual Router Redundancy Protocol) and describes how to
configure VRRP on the Corecess S5 System.
The VRRP router controlling the IP addresses associated with a virtual router is called the
Master. The Master forwards packets on behalf of these IP addresses. VRRP supports one IP
address for each virtual router. VRRP provides redundant gateways without any changes to the
host's configuration while supporting standard based routing protocols. As a result, any of the
virtual router's IP addresses on a LAN can then be used as the default first hope router by end
host.
The following figure shows a basic VRRP configuration uses a single VRID (VRID 1):
Subnet 2
RTA RTB
(Master) (Backup)
VRID 1
10.0.0.1
Default
Subnet 1 gateway:
Because RTA is the address owner, it serves as the master. RTB is the backup. The three end
hosts on subnet 1 are configured to use 10.0.0.1/8 as the default router. IP address 10.0.0.1 is
associated with VRID 1.
As shown in this example, if RTA becomes unavailable, RTB takes over VRID 1 and its
associated IP addresses. Packets sent to IP destinations outside the 10.x.x.x subnet using 10.0.0.1
as the router are then forwarded by RTB. Even though RTB assumes RTA's forwarding
responsibilities, it never processes any packet with destination address (DA) 10.0.0.1. When
RTA becomes active again, it takes over as the master and RTB reverts to backup.
Configuring VRRP
This section describes how to configure VRRP on the Corecess S5 System.
When configuring VRRP on the Corecess S5 System, consider the following contents.
The IP addresses associated with the VRID must already be configured on the router that will be
the Master router.
The IP addresses associated with the VRID must be on only one router
The VRRP advertisement interval must be set to the same value on both the Master and Backups
for the VRID.
1. Configuring IP interfaces
Before you configure VRRP, you must configure an IP interface and assign a primary IP address
and subnet mask. To configure an IP interface and IP address, use the following commands:
Command Description
configure terminal 1. Enter Global configuration mode.
The following example shows how to configure the VLAN interface and assign a primary IP
address and subnet mask:
To create a VRRP virtual router on the Corecess S5 System, use the following command:
Command Description
configure terminal 1. Enter Global configuration mode.
router vrrp 2. Create a VRRP virtual router and enter VRRP configuration mode.
<virtual- <virtual-router-id>: The identifier of the virtual router to create.
router-id> (1 ~ 255)
end 3. Return to Privileged mode.
show vrrp 4. Verify the VRRP virtual router configuration.
The following example creates a virtual router with an identifier (VRID) of 1 and enters VRRP
configuration mode:
# configure terminal
(config)# router vrrp 1
(config-vrrp)# end
# show vrrp
VrId <1>
State is Initialize
Virtual IP is unset
Interface is unset
Priority is unset
Advertisement interval is unset
Preempt mode is TRUE
#
After creating a virtual router, specify the IP address and operation mode for the virtual router.
If the operation mode for the virtual router is master, you should specify the IP address for the
Master router to the real IP address configured on the Master router.
To configure the IP address and operation mode for the virtual router, use the virtual-ip
command in VRRP configuration mode:
Command Description
The following example configures the IP address for the Master router to the IP address 10.0.0.1
of the default VLAN interface:
The priority for the virtual router is used to elect the Master router. If two backup routers have
the same priority, the router that has the highest primary address becomes the master.
The default value for the Master is 255 and the default value for the Backups is 100. To
configure priority for the virtual router, use the priority command in VRRP configuration
mode.
Command Description
priority <priority> <priority>: Priority value of the VRRP router. The range is 1 ~ 255.
The following example sets the priority for the virtual router to 254:
The advertisement interval must be the same across the set of VRRP routers that are associated
with a single VRID. Backup routers must have the same advertisement interval as the Master
router.
The default VRRP advertisement interval is 1 second. To configure the VRRP advertisement
interval time, use the advertisement-interval command in VRRP configuration mode.
Command Description
The following example Sets the interval time between sending advertisement packets to 5
seconds:
Even if the master router has already been decided, if there is a backup router that has higher
priority, preempt mode decides whether the backup router should be specified as a master
router.
Command Description
true If there is a backup router that has higher priority, the backup router is
preempt-mode specified as a master router.
{true | false} false Even if there is a backup router that has higher priority, the backup
router cannot be specified as a master router.
The following example shows how to set the preempt mode to false:
Simple Password : Authenticate using the specified characters (authentication key). When a
VRRP packet is transmitted and received, compare the authentication key and VRRP packet
key. If the VRRP packet has no key, or the authentication key does not match with the VRRP
packet key, the VRRP packet is discarded.
The Corecess S5 System uses Simple Password by default. To set the authentication type and
(optionally) an authentication key to be used by a VRRP virtual router, use the following
commands in Interface configuration mode:
Command Description
ip vrrp authentication <key> : The authentication key to use when sending and
string <key> receiving VRRP packets. (1 ~ 8 character)
The following example shows how to specify simple password for VRRP authentication on the
default VLAN interface whose ID is 1.
After configure all VRRP parameters, enable the virtual router on the interface owns the IP
address of the virtual router as follows:
Command Description
interface vlan
{id <vlan-id> | 1. Enter Interface configuration mode.
name {vlan- <vlan-id>: VLAN ID (1 ~ 4094)
name>} <vlan-name>: VLAN name
ip vrrp
2. Enable a specific VRRP instance on the VLAN interface.
<virtual-
<virtual-router-id>: Virtual router ID (1 ~ 255)
roiter-id>
exit 3. Return to Privileged mode.
router vrrp 4. Verify the virtual router configuration.
The following example enables the VRRP instance 1 on the VLAN interface:
When Uplink interface of VRRP master router becomes down due to failure, VRRP backup
router should be enabled to converted to new VRRP master. For this, monitor Up/Down
function of Uplink interface by setting VRRP Track function on Uplink interface.
VRRP tracking interface sets VRRP Virtual Router Id on Uplink Interface to monitor failure, and
when interface is down, sets Priority Delta value to be decreased. When relevant interface of
VRRP master router is down, decrease priority value as much as Priority Delta value, and when
priority value of VRRP backup router is higher than mater router, backup router is converted to
new VRRP master router.
Command Description
The followings are examples of activating Tracking interface on VRRP virtual router.
(config)# interface vlan id 1
(config-if)# ip vrrp 1 tracking decrement 50
(config-if)# end
# show vrrp
VrId <1>
State is Shutdown
Virtual IP is 10.0.0.1 (IP owner)
Interface is vlan1
Priority is 255
Advertisement interval is 1 sec
Preempt mode is TRUE
Tracking Interface vlan10, Priority Delta 50, Status UP
#
The following are example of releasing setup of VRRP Tracking interface.
(config)# interface vlan id 1
(config-if)# no ip vrrp 1 tracking
(config-if)# end
Internet Internet
RTA RTB
(Master) (Backup)
Interface: VRRP_1 (VLAN Interface: VRRP_2 (VLAN
GE 5/1 GE 5/1
ID:2) ID:3)
VRID: 1 VRID: 1
IP address: 192.53.5.1 IP address: 192.53.5.1
Priority: 255 Priority: 100
Default
gateway:
RTA
(config)# vlan id 2 name VRRP_1
(config)# vlan id 2 port gigabitethernet 5/1
(config)# interface vlan id 2
(config-if)# ip address 192.53.5.1/32
(config-if)# exit
(config)# router vrrp 1
(config-vrrp)# virtual-ip 192.53.5.1 master
(config-vrrp)# exit
(config)# interface vlan id 2
(config-if)# ip vrrp 1
(config-if)# end
# show vrrp
VrId <1>
State is Master
Virtual IP is 192.53.5.1 (IP owner)
Interface is vlan2
Priority is 255
Advertisement interval is 1 sec
Preempt mode is TRUE
#
RTB
(config)# vlan id 3 name VRRP_2
(config)# vlan id 3 port gigabitethernet 5/1
(config)# interface vlan id 3
(config-if)# ip address 192.53.5.3/32
(config-if)# exit
(config)# router vrrp 1
(config-vrrp)# virtual-ip 192.53.5.1 backup
(config-vrrp)# exit
(config)# interface vlan id 3
(config-if)# ip vrrp 1
(config-if)# end
# show vrrp 1
VrId <1>
State is Backup
Virtual IP is 192.53.5.1 (Not IP owner)
Interface is vlan3
Priority is 100
Advertisement interval is 1 sec
Preempt mode is TRUE
#
# show vrrp 1
VrId <1>
State is Master
Virtual IP is 192.53.5.1 (IP owner)
Interface is vlan2
Priority is 255
Advertisement interval is 1 sec
Preempt mode is TRUE
Tracking Interface vlan10, Priority Delta 50, Status UP
#
The following table describes the fields in the show vrrp command output:
Field Description
The VRID configured on this interface. If multiple VRIDs are configured on
VrId
the interface, information for each VRID is listed in a separate row.
The VRRP state for the VRID. The state can be one of the following:
State - Backup: This switch is a Backup for the VRID.
- Master: This switch is the Master for the VRID.
Virtual IP The virtual IP address that is being backed up by the VRID.
The interface on which VRRP is configured. If VRRP is configured on
Interface
multiple interfaces, information for each interface is listed separately.
Priority The current VRRP priority for the VRID (0 ~ 255)
Advertisement interval VRRP advertisement packet interval (1 ~ 10 seconds)
preempt mode Indicates whether to preemption is enabled or not.
Tracking Interface Tracking interface of virtual router
VRRP Commands
The following table lists the commands for configuring VRRP on the Corecess S5 System and
displaying VRRP configuration:
Command Description
ip vrrp authentication
Configures the authentication type for a virtual router interface.
mode
router vrrp Creates a VRRP virtual router and enter VRRP configuration mode.
virtual-ip Configures the IP address and operation mode for a virtual router
ip vrrp tracking
Enable Tracking interface of VRRP virtual router
decrement
RADIUS Management
Remote Authentication Dial In User Service (RADIUS) is an AAA (authentication, authorization,
and accounting) protocol for controlling access to network resources by Server/Client method.
Corecess product series support RADIUS server and Proxy Server functions for Dot1x and
PPPoE Authentication Service.
Accounting start
If do Accounting, you must enable function in relevant interface. You must execute command at
interface node as follows.
Interim-Report
Interim Report's execution availability and setting of time frame can do separatively in each
interface.
If you do following setting, it send Interim-Report to Accounting server every 5 minutes.
Framed-IP-Address
Subscriber can send attaching Internet Protocol Address that subscriber is using on accounting
packet when offer L3 service.
Nas-Port/Nas-Port-Type
Service Manager recognizes each subscriber of interface and apply setting of the interface to
subscriber. These point businessman can configure account to unique policy by interface.
The present subscriber attaches interface and type of relevant interface on Service Manager's
accounting packet to help this.
Each interface executes unique RADIUS Proxy Server. This time, relevant interface is Enabled
state and L3 interface that have Internet Protocol Address.
Parameters
* Shared Secret
Each Proxy RADIUS Server processes RADIUS Client's Request that have unique Key and have
Key that agree. Each interface has independent Key and can keep the best security state.
* realm-stripping
RADIUS Proxy Server finds server to do Forwarding using Realm that is included in Request's
User-name field that arrive. This time, you can remove request's user-name field realm that do
forwarding.
* Access List
Service Manager supports that register Access List by RADIUS Proxy Server of each interface
and elutriate packet to control illegal RADIUS Client's access.
TACACS Management
Configuring TACACS Management.
TACACS allows a remote access server to communicate with an authentication server in order
to determine if the user has access to the network. The following commands in table are
configuration commands for managing TACACS.
aaa : IP information
tacacs : TACACS+
aaa tacacs source-interface source-interface : Select an interface to configure
config
loopback id <1-32>
loopback : Loopback Interface
id : Loopback Interface ID
You can disable TACAS management configuration with the following commands.
Accounting
Authentication
Authorization
802.1X(dot1x)
All the setting of 802.1X of Corecess products is on interfaces each. It means that each of
interfaces gives us specific services. The 802.1X of Corecess products does not support the port-
based authentication that certifies a specific port, but also supports mac-based authentication
that certifies subscribers each.
localhost#
localhost# configure terminal
localhost(config)# interface vlan id 100
localhost(config-if)# dot1x port-based
localhost(config-if)# end
localhost#
You can specify back-end Authentication Server using following CLI commands.
* RADIUS
Configuring back-end Radius of 802.1X is as follows;
nas-ip setting : Nas-ip of equipment for communication with radius server setting .
Parameters
Re-authentication
Whenever re-authperiod does expire, Corecess 802.1X sends EAP-Request Identity frame to
subscriber and re-authentication does beginning (trigger). Once re-authentication beside such
periodic re-authentication is available. Administrator can do as receive authentication newly
using following command when catch abnormal operation from specification subscriber.
Subscriber at the same time that command is executed changes and begins authentication newly
by state (unauthorized) that authentication does not become.
* MAC Control
Corecess 802.1X does access control by subscriber unit that physical port unit is not with that is
described to white paper. This time, about specification subscriber, you can do fixed setting
(Authorized/Unauthorized).
localhost# conf t
localhost(config)# inter vl id 100
localhost(config-if)# dot1x mac-control force-authorized a:b:c:d:e:f
localhost(config-if)# dot1x mac-control force-unauthorized 0:0:ff:ee:aa
While subscriber a:b:c:d:e:f becomes in authentication success state at the same time connection,
0:0:ff:ee:aa is impossible authentication. These setting can be terminated through following CLI
command. Relevant subscriber passes through general IEEE 802.1X authentication procedure
and receive authentication since the terminated moment.
The Quiet Period and the Tx Period do following function by FSM parameter of IEEE 802.1X.
Parameter Description
Subscriber who fail in authentication cannot begin new authentication during Quiet
Quiet Period
Period interval.
After send EAP-Response, think that subscriber disappears in case there does not exist
Tx Period
when sent as Tx Period.
Status
Corecess 802.1X supplies following state information to administrator.
session(subscriber) information
statistics information
802.1X Session
----------------------------------------------------------------------
0a:0b:0c:0d:0e:0f(static entry)
Identity:
Interface: vlan100
FORCE_AUTHORIZED
REAUTH_INITIALIZE
EAPoL
=============================
Received = 0
Sent = 1
EAPoL Success = 1
EAPoL Fail = 0
EAPoL Start = 0
EAPoL Log-off = 0
EAPoL Resp/ID = 0
EAPoL Req/ID = 0
EAPoL Invalid = 0
Length Error = 0
Last Version = 0
Last Source MAC= 00:00:00:00:00:00
Back-end
=============================
Received = 0
Sent = 0
Timeout = 0
Redundancy Configurating
This clause introduces the ‘Redundancy’ provided from Corecess S5 System, and reviews how
to configure redundancy.
Corecess S5 System supports various redundancies such as POWERE, FAN, Control Module,
SLS(Seed Light Source),EPON LineCard and others.
The Control Module Redundancy of Corecess S5 System redundates the two Control Modules
between No.9 slot (A-Side SCM) and No.10 slot (B-Side SCM) of S5 in order that the cutoff of
service may not be minimized in case a Control Module fails.
To secure more stable service, the redundancy of Epon LineCard redundates two Epon
Linecards (or two Epon Ports) so that the cutoff of service may be minimized in case an Epon
LineCard (or two Epon Ports) fails.
Moreover S5 System Support the redundancy. with two SLS devices and WDM module
cards(GW-16GF) for WDM-PON Service.
System Resources(cont.)
Power Modules: 2:1 Protection
2 DC modules : 1 (operational) + 1 (stand-by)
4 * 1G SFP Ports :
4* 1G TX Ports :
Power Features - DC
Electrical Specification
Input Range: DC-40V ~ -72V
Rating: DC -48V
Function
Redundant power line : load sharing
Protection
Reversed connection of input power line
Surge(IEC61000-4-5)
Mechanical specification
Input terminals: FG, RTN, -48VDC
Power Features – AC
Electrical Specification
Input Range: AC90V ~ 264V
Frequency : 50/60Hz
Function 2:1
1+1 ACProtection
Power module
Redundant power module : load sharing
Protection
Input over current
Surge(IEC61000-4-5)
Mechanical specification
Input terminals: AC inlet socket
Epon Redundancy
The following instructions are used to manage the redundancy of Epon LineCard.
Command Description
configure terminal 1. Global configuration mode is set in
redundancy epon- 2. This instruction Enables the redundancy of new Epon LineCard.
module <active slot> Line Card Number to provide the present service
<active slot> <standby slot> Line Card number to be used as the
<standby slot> backup of <active slot>
show redundancy This instruction checks the list of redundated Epon LineCards and those
epon-module state.
redundancy epon-
module ※ Active/Standby roles of two Epon LineCards are changed with each
<active slot> other.
<standby slot> switch
localhost# con t
localhost(config)# redundancy epon-module 1 6 switch
localhost(config)# exit
localhost# show redundancy epon-module
------------------------------------------------------------
6 insert,up 1 insert,up,optic-disable
localhost# con t
localhost(config)# no redundancy epon-module 6 1
localhost(config)# exit
localhost# show redundancy epon-module
localhost#
The following are used to manage the redundancy of Epon Port. It is basically identical to the
redundancy of Epon LineCard. The two ports on the same Epon LineCard can be redundated as
well as the redundancy between different Epon LineCards can be possible.
Command Description
configure terminal Global Configuration Mode is set in.
This instruction Enables the redundancy of new Epon Port.
port epon
<active slot/port> Epon Port number to provide the present
<active slot/port>
service
redundancy
<standby slot/port> Epon Port number to be used as
<standby slot/port>
the backup of <active slot/port>
port epon WORD Switching redundancy epon port.
redundancy WORD
switch
redundancy epon-port Switching delay time setting<0-65535>sec.
switch_delay <0- Disabling command:
65535> no redundancy epon-port switch_delay.
show redundancy 3. This instruction checks the list of redundated Epon LineCards and
epon-port those state.
port epon
<active slot/port> ※ Active/Standby roles of two Epon LineCards are changed with each
redundancy other.
<standby slot/port>
Caution: When you execute ‘no port epon WORD redundancy WORD’ command, It
stop transmitting signal to ONT.
localhost# con t
localhost(config)# port epon 6/1 redundancy 6/2 switch
localhost(config)# exit
localhost# show redundancy epon-port
localhost# con t
localhost(config)# no port epon 6/2 redundancy 6/1
localhost(config)# exit
localhost# show redundancy epon-port
The redundant SCM transmits the data(Protocol) to the Stand-by through the RR(Record replay)
when the data of active routing table is updated. And standby SCM updates the routing table
with it. According to this process, RIB of Active-standby SCM continues to make a
synchronization. After a switchover, the new active SCM routing protocol gets the routing table
of local RIB module through the graceful-restart process and makes a synchronization with a
neighbor router through the routing state machine.
You have to configure graceful restart each routing protocol for the redundancy.
As RIP graceful-restart does not need the complex negotiation mechanism with each neighbor,
it’s more simple than OSPF or BGF. It’s not necessary to configure an additional helper mode
router.
The next is the command of graceful restart configuration for RIP redundancy.
Command Description
[no] rip restart
2. Set rip graceful restart configuration
grace-period <1-
<1-65535> grace period (seconds)
65535>
localhost# con t
localhost(config)# rip restart grace-period 120
localhost(config)# exit
Receiving Mode
RIP configuration
router rip
network 3.3.3.0/24
network 30.30.30.0/24
network 40.40.40.0/24
!
rip restart grace-period 180 2:1 Spliter
!
Restarting Mode
RIP configuration
Active Standby
RIP RIP
router rip
network 3.3.3.0/24
network 10.10.10.0/24
network 20.20.20.0/24
!
rip restart grace-period 180
!
FIB FIB
S511
The next is the command of graceful restart configuration for OSPF redundancy.
Restarting Mode
As restarting mode is to configure to the system that the routing protocol restarts, you have to configure
the redundant S5 system to restarting mode.
Helper Mode
The router, the neighbor of the restarting router system must be configured to helper mode. In other
words, the router system connected with the uplink of S5 have to support the graceful restart helper mode.
While a restarting router restarts, a helper router does not routing information during the grace-period.
And it’s a role to flood the routing information to the neighbor router continuously
Command Description
configure terminal 1. Enter Global configuration mode.
Example 1) The following example shows how not to run ospf helper mode.
localhost# con t
localhost(config)# ospf restart helper never
localhost(config)# exit
Example 2) This following example show hot to run ospf helper mode.
localhost# con t
localhost(config)# ospf restart helper max-grace-period 120
localhost(config)# exit
Helper Mode
OSPF configuration
ospf restart helper max-grace-period 180
!
router ospf
network 3.3.3.0/24 area 0
network 30.30.30.0/24 area 0
network 40.40.40.0/24 area 0
2:1 Spliter
!
Restarting Mode
OSPF configuration
Active Standby
ospf restart grace-period 180
OSPF OSPF
!
router ospf
network 3.3.3.0/24 area 0
network 10.10.10.0/24 area 0
network 20.20.20.0/24 area 0
!
FIB FIB
S511
The next is the command of graceful restart configuration for BGP redundancy .
Command Description
configure terminal 1. Enter Global configuration mode.
Receiving Mode
BGP configuration
router bgp 200
bgp graceful-restart restart-time 180
network 3.3.3.0/24
network 30.30.30.0/24
network 40.40.40.0/24
neighbor 3.3.3.1 remote-as 100
neighbor 3.3.3.1 capability graceful-restart 2:1 Spliter
!
Restarting Mode
BGP configuration
router bgp 100
Active Standby bgp graceful-restart restart-time 180
BGP BGP network 3.3.3.0/24
network 10.10.10.0/24
network 20.20.20.0/24
neighbor 3.3.3.2 remote-as 200
neighbor 3.3.3.2 capability graceful-restart
!
FIB FIB
S511
Command Description
configure terminal 1. Enter Global configuration mode.
[no] isis restart
2. Set isis to restarting mode.
grace-period <1-
<1-65535> : grace period (seconds)
65535>
[no] isis restart
3. Set isis to helper mode.
helper
interface vlan id <1-
4. Enter interface configuration mode.
4094>
5. Set hello-interval value of restart progress.
[no] isis restart-
<1-65535> : hello-interval value (seconds)
hello-interval <1-
level-1 : level-1 IIHs
65535>
level-2 : level-2 IIHs
localhost# con t
localhost(config)# isis restart helper
localhost(config)# exit
Helper Mode
IS-IS configuration
Active Standby
IS-IS IS-IS
Restarting Mode
IS-IS configuration
isis restart grace-period 180
!
inteface vlan id 20
FIB FIB ip address 20.20.20.1/16
ip router isis
isis restart-hello-interval 180
!
router isis
net 49.0001.0200.2002.0001.00
!
S511
FAN [ 1] Normal
FAN [ 2] Normal
FAN [ 3] Normal
FAN [ 4] Normal
FAN [ 5] Normal
FAN [ 6] Normal
FAN [ 7] Normal
FAN [ 8] Normal
Auxiliary Information
-----------------------------------------------------------------------------
Fan (`C(`F)) -
Max/Min Threshold : 33/ 25 ( 91/ 77)
Temperature (`C(`F)) -
Current Temperature : 42 (107 )
Max/Min Threshold : 90/ 80 (194/176)
-----------------------------------------------------------------------------
MIB-II: System Group
Contact: support@corecess.com
Name: Corecess S5
Location: Corecess Inc.
Descr: Switched Router
ObjectID(36): 1,3,6,1,4,1,2971,50,46
localhost#
My Side Info.
------------------------------------------------------
State ................................... Active
Version ................................. $Revision: 1.1 $
Instructions of Redundancy
The following table shows sorts of the instructions, related with the redundancy supported
from Corecess S5 System, and their functions.
Command Description
system redundancy mode This instruction sets redundancy mode.
This instruction converts Standby Control Module into new
system redundancy switchover
Active.
system redundancy uplink port This instruction Enables the redundancy of uplink port.
reset control-module This instruction reboots just the related Control Module.
copy flash image standby This instruction copies the software image file of Active
module into standby.
copy standby flash config This instruction saves the configuration information of
startup—config Standby module into startup-config.
copy standby startup-config flash This instruction saves startup-config of Standby module into
config new configuration information file.
This instruction deletes the configuration information file of
delete standby flash config
Standby module.
delete standby flash image This instruction deletes the software image file of Standby
module
This instruction applies new software image of Standby
update standby flash image
module.
show system redundancy This instruction check the state information of redundancy.
show system redundancy mode This instruction checks the setup of redundancy mode.
This instruction checks the state information of redundant
show system redundancy uplink
uplink.
This instruction checks the state information of redundant
show system redundancy uplink
uplink.
Hardware Specifications
Table A-1 Corecess S5 System hardware specifications
Item Specification
Switching Fabric
Memory
Power Redundancy
Operational
Temperature
Environment
Cables
Packages Console Cable (RJ-45 – DB-9)
DC Power Cable (5m)
Manual
Software Specifications
Table A-2 Corecess S5 System software specifications
Item Specification
VLAN Function
Support Port based VLAN, IEEE 802.1q tagged VLAN and overlap VLAN (Maximum
4,096)
Support Spanning Tree and Multicast per VLAN
Link aggregation Function
Routing Function
Static
RIP
OSPF
IS-IS
BGP4
VRRP
Multicasting Function
IGMP v2.0
IGMP snooping
PIM-SM/DM
Function
DVMRP
QoS Function
Security Function
Access List
MAC Filtering
DHCP Filtering
NetBIOS Filtering
Management Function
Console
- Local : RJ-45 Console Port (Out-band)
- Remote : Telnet and Web based Console (In-band)
CLI (In-band, Out-band)
NMS (ViewlinX Manager/EMS)
Port mirroring
Function
SNMP v1/v2c
RMON
- Group 1 (Statistics), Group 2 (History), Group 3 (Alarm), Group 9 (Events)
- Extended RMON
System log file (configuration log)
Remote software upgrade (FTP/TFTP)
System fan status monitoring and control
RFC 768 UDP
RFC 791 IP
RFC 792 ICMP
RFC 826 ARP
RFC 768 UDP
RFC 783 TFTPv2
RFC 793 TCP
RFC 826 ARP
RFC 854 Telnet
RFC 927 TACACS+
RFC 951 BOOTP
RFC 1058 RIP v1
RFC 1075 DVMRP
RFC 1112 Host Extensions for IP Multicasting
RFC 1157 SNMPv1
RFC 1165 NTP
IETF RFC 1195 IS-IS
Standard RFC 1245 OSPF Protocol Analysis
RFC 1246 Experience with the OSPF Protocol
RFC 1256 ICMP Router Discover Message
RFC 1265 BGP Protocol Analysis
RFC 1266 Experience with the BGP Protocol
RFC 1349 Type of Service in the Internet Protocol Suite
RFC 1403 BGP OSPF Interaction
RFC 1519 CIDR: an Address Assignment and Aggregation Strategy
RFC 1541 DHCP(Dynamic Host Configuration Protocol)
RFC 1542 Clarifications and Extensions for the Bootstrap Protocol
RFC 1583 OSPF v2
RFC 1587 OSPF NSSA Option
RFC 1656 BGP v4
RFC 1657 Definitions of Managed Objects for BGP-4 using SMIv2
RFC 1723 RIP v2
RFC 1745 BGP-4/IDRP for IP and OSPF Interaction
RFC 1765 OSPF Database Overflow
Item Specification
Number of
32
Branched
Average : 17.0 dB
Insertion Maximum : 18.0 dB
Loss Uniformity : ≤ 1.9 dB
PDL : ≤ 0.3 dB
Return
Optical > 55dB
Loss
Specification
Directivity > 55dB
Operating
wavelengt 1.26 ~ 1.60 um
h
Input : Diameter 250μm
Pigtails Output : Ribbon fiber
Average length: 1M
Temperature
Operating Range: Commercial Version: 0℃ ~ 50℃
Extended Commercial Version: - 20℃ ~ 60℃
Environment Hardened version: - 40℃ ~ 65℃
Storage Range : -40 ~ 80°C
Humidity
Appendix B describes the specifications of the ports on the Corecess S5 System. In addition, the kinds and
specifications of cables needed for the connection of each port.
Connector Specifications
Connector Specifications
RJ-45 Connector
10/100/1000Base-T Port
10/100/1000Base-T port on the SCM,LIM module has an 8-pin RJ-45 connector. The
cable used for connecting 10/100/1000Base-T port is twisted-pair cable with RJ-45
8 1 connectors at both ends.
Ethernet Management port on the SCM module has an 8-pin RJ-45 connector. The cable
used for connecting Ethernet Management port is twisted-pair cable with RJ-45
8 1 connectors at both ends.
Pin Signal
1 Rx+
2 Rx-
3 Tx+
6 Tx-
Pin Signal
3 Tx
4 GND
5 GND
6 Rx
LC Connector
1000Base-SX/LX/LH/ZX Transceiver
SC Connector
In the case that 1000BASE-PX optical transceiver is applied to the optical port
for EPON and 1000BASE-BX optical transceiver is to the optical port for GbE, the
receiving and transmitting wavelength are 1310/1490 nm in each. In that case,
Cable Specifications
Twisted Pair Cable
The Ethernet Management port and 10/100/1000Base-T port on The SCM-208G module are
connected by using twisted pair cables with RJ-45 connectors at both ends.
There are two types of twisted pair cables: UTP (unshielded twisted pair) cable and STP
(shielded twisted pair) cable. The following figure shows a twisted pair cable with RJ-45
connectors at both ends.
The category of twisted pair cable to be used is determined by the speed of the devices to be
connected to RJ-45 port. In case of connecting with a device that operates at 10Mbps, category 3
and 4 cable is used. In case of connecting with a device that operates at 100Mbps, category 5
cable is used. In case of connecting with a device that operates at 1000Mbps, category 5+ or
category 6 cable is used.
Either straight-through cable or crossover cable is used according to the kinds of devices to be
connected to RJ-45 port. In case the device to be connected is such terminal (MDI) as PC
equipped with NIC (Network Interface Card), straight-through cable is used. On the other hand,
crossover cable is used for connecting the ports of network devices (MDI-X) such as hub or
switch.
Table B-4 System Modules with Fiber Optic Ports Duplex LC Fiber Optic Cable
Fiber Optic
Module Connector Interface Wave Length(nm)
Cable
1000Base-SX Multi-mode Rx/Tx : 850nm
GW-PON
LIM-GW16GF Simplex SC/APC Single mode Rx/Tx:1535~1560nm
(16CH GbE)
The orange-colored multi-mode fiber(MMF) is used for the 1000Base-SX transceiver in the
transporting distance less than 550m.
Orange
Note: Before connecting the console port, ensure that console terminal is configured as
follows:
Appendix C Maintaining
Caution: Before you install the Corecess S5 system, read ‘Chapter3 Before Installation’.
‘Chapter 3’ contains important safety information you should know before working with the
system.
Replacing Module
Replacing Module
If a module installed in a slot has a problem, the module can replace new one. This section
describes how to replace SCM modules and LIM modules on the Corecess S5 System.
Example: S5-CH
Corecess S511
LIM Slot (1 ~ 8)
Corecess S506
SCM Slot (5)
LIM Slot(1 ~ 4)
Caution : Be careful not to install modules into the wrong slots when you replace several
modules. Be sure
to confirm module location before installation.
Required Tool
If you replace modules installed in the Corecess S5 System, the following tools are required.
Before replacing modules, prepare the tools.
A screwdriver
Electrostatic discharge (ESD) grounding strap
Replacing Modules
The replacing procedure of installed module in the Corecess S5 System is as follows:
Note: Since the Corecess S5 System provides the hot-swap functions, the system power
doesn’t have to be turned off.
Warning: Do NOT put your fingers into slots if the system is not turned off. You might
receive an electric shock by the back-plain or power supply.
1. Execute the write memory command in the Telnet session which is connected to the
Corecess S5 System to store current system configuration in the backup configuration file.
4. Push the ejector levers on the both side of the module to release locked state, then pull the
ejector levers outward and extract the module carefully from the chassis.
5. Prepare a module that is to be installed. Place the module to the guide rail that is located in
the both sides of the slot. Then, insert the module carefully until it gets installed in the
connector of the back plane.
6. Push the ejector levers inward, then the module installed completely with the connector of
back plane.
7. Fasten the module firmly by tightening the two screws using a screwdriver.
8. If the module is installed successfully, the Run LED on the module is turned on with green.
Maintaining 18-3
Replacing Fan Tray
Caution: Do NOT operate the system when you replace the fan tray. If the fan tray is not
operating, the system can be damaged by the overheat.
1. Check the Fan LED on the system fan tray. The Fan LED is turned on with red when the
fan tray has a problem.
3. Grasp the handle of the fan tray and gently pull it.
4. Prepare new fan tray. Slide the new fan tray into the chassis until the rear of the fan tray
plugs into the corresponding connector on the back-panel.
5. Fasten the fan tray firmly by tightening the screw using a screwdriver.
6. If the fan tray is installed successfully, the LED on the fan tray is turned on with green.
The following procedure describes how to clean the fan filter in the Corecess S5 System.
1. Grasp the handle of the fan filter, and gently pull it forward until the fan filter is
separated from the chassis. At this time, be sure not to scatter dust of the fan filter.
2. Check the fan filter state. If there is a lot of dust or dirty in the fan filter, remove dust
with a vacuum machine or wash the fan filter with a neutral detergent. When you clean
the fan filter with water, install spare fan filter in the chassis.
3. If you wash the fan filter with a neutral detergent, dry the fan filter in cool place over
eight hours.
4. After cleaning, insert the fan filter into the slot of the chassis.
Maintaining 18-5