cc/td/doc/product/ong/15305/cecdocs
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table Of Contents

Layer 2 Configuration

7.1  Bridge

7.1.1  Configuration of Static Unicast Forwarding Information Example

7.1.2  Configure Static Multicast Forwarding Information

7.1.3  Enable IGMP Snooping

7.2  Spanning Tree Protocol (STP) Configuration

7.2.1  Configure the STP Algorithm per Device

7.2.2  Configure the STP Algorithm per VLAN

7.3  Rapid Spanning Tree Protocol Configuration

7.3.1  Configure RSTP on a Port

7.4  MAC Multicast

7.4.1  Configuring MAC Multicast

7.5  Traffic Control

7.5.1  PortPriority

7.5.2  PriorityGroup

7.5.3  TrafficClass

7.6  Manage VLANs

7.6.1  Virtual Local Area Networks (VLAN)

7.6.2  Tagged/Untagged LAN Ports

7.7  VLAN Provisioning

7.7.1  Configure a New VLAN Per Port

7.7.2  Configure a New VLAN Per Protocol and Per Port

7.7.3  Configure an Ethernet User Defined Protocol

7.7.4  Configure VLAN Port members

7.7.5  GVRP

7.8  Examples

7.8.1  Configuration of an IP Interface

7.8.2  Configuration of a Static Route

7.8.3  Configuration of a RIP Filter

7.9  Open Shortest Path First

7.9.1  Supported OSPF Areas: Transit and Stub Areas

7.9.2  Configure an OSPF Area

7.9.3  Configure an OSPF Interface

7.9.4  Enable OSPF on the Network Element

7.10  DHCP

7.10.1  Configure the Range of IP Addresses for the DHCP Server


Layer 2 Configuration

This chapter explains how to manage the bridging service (L2 forwarding) on the network element and includes:

•Presentation and modification of the bridge.

•Presentation and modification of MAC Multicast and IGMP Snooping.

•Presentation and modification of spanning tree protocol (STP) and Rapid STP (RSTP).

•Presentation and modification of traffic control.

•Presentation and modification of virtual local area network (VLAN).

Note The following examples focus on ONS15305, but the the features described also apply to the ONS 15302.

7.1  Bridge

This chapter describes the configuration operations supported by the Bridge managed object.

For troubleshooting information, see Appendix A, "Troubleshooting and FAQ." It also contains tips and answers to several frequently asked questions.

7.1.1  Configuration of Static Unicast Forwarding Information Example

Use the following steps to configure an entry in the MAC unicast forwarding table ( Figure 7-1).

Step 1 Click on the ONS 15305 managed object, then click the Bridge managed object in the topology browser.

Step 2 Double-click unicastForwarding in the attributes window.

Figure 7-1 Configuration of Static Unicast Forwarding Information

.

Step 3 Click Add on the toolbar.

Step 4 The following attributes have no default values and must be defined:

•bridgePortNumber

Set the bridge port number of the port through which the MAC address can be reached.

•macAddress

Set the MAC address. The MAC address must be a unicast address.

•vlanId

Set the VLAN ID for which this entry applies.

•deleteStatus

Set permanent if the entry should not be removed dynamically from the table (such an entry will stay over a reset of the bridge). Set deleteOnReset if the entry should be removed dynamically from the table after the next reset of the bridge. Set deleteOnTimeout if the entry should be dynamically aged out by the bridge.

Step 5 Click Save on the toolbar.

7.1.2  Configure Static Multicast Forwarding Information

See the "Question 5" section on page A-2 before you begin configuring an entry in the MAC multicast forwarding table ( Figure 7-2).

Step 1 Click on the ONS 15305 managed object, and then click the Bridge managed object in the topology browser.

Step 2 Double-click MACMulticast, then double-click MulticastStatic in the attributes window.

Figure 7-2 Configuration of Static Multicast Forwarding Information

.

Step 3 Click Add on the toolbar.

Step 4 The following attributes have no default values, and must therefore be defined:

•vlanId

Set the VLAN ID for which this entry applies.

•MacAddress

Set the MAC address. The MAC address must be a multicast address.

•staticBridgePortNumbers

Set the set of ports through which the multicast/broadcast frame must be forwarded regardless of any dynamic information. The set of ports is entered as an octet string where each bit represents one port, for further information see also Appendix A, "Troubleshooting and FAQ."

•forbiddenBridgePortNumbers

Set the set of ports through which the frames must not be forwarded regardless of any dynamic information. The set of ports is entered as an octet string where each bit represents one port, for further information see also Appendix A, "Troubleshooting and FAQ."

•status

Set permanent if the entry should not be removed dynamically from the table (such an entry will stay over a reset of the bridge). Set deleteOnReset if the entry should be removed dynamically from the table after the next reset of the bridge. Set deleteOnTimeout if the entry should be dynamically aged out by the bridge.

Step 5 Click Save on the toolbar.

Note When a multicast forwarding information is added to the table, the same entry is automatically added to the Bridge > macMulticast >multicastForwarding attribute. The multicastForwarding attribute contains both static, that means user-defined, and learned entries related to group (multicast) addresses.

7.1.3  Enable IGMP Snooping

When a host wants to receive multicast traffic, it must inform the routers on its LAN. The IGMP is the protocol used to communicate group membership information between hosts and routers on a LAN. Based on the information received through IGMP, a router forwards multicast traffic only via interfaces known to lead to interested receivers (hosts).

On the contrary, bridges flood multicast traffic out all ports per default, and therefore waste valuable network resources. IGMP snooping on a bridge can eliminate this inefficiency. IGMP snooping looks at IGMP messages to determine which hosts are actually interested in receiving multicast traffic. Based on this information, the bridge will forward multicast traffic only to ports where multicast receivers are attached.

Complete the following steps to enable IGMP snooping on the network element ( Figure 7-3).

Step 1 Click on the ONS 15305 managed object, and then on the Bridge managed object in the topology browser.

Step 2 Click on the macMulticast attribute in the attribute window.

Step 3 Set the macMulticastEnable attribute to enabled.

Step 4 Click on the igmpSnooping attribute in the attribute window.

Step 5 Set the igmpSnoopingEnable attribute to true.

Step 6 Click Save.

Figure 7-3 Enabling IGMP Snooping

7.2  Spanning Tree Protocol (STP) Configuration

The STP allows layer 2 devices to discover a subset of the topology that is loop-freebut still has a path between every pairs of LANs.

The network element can run either one single STP algorithm for the whole device (perDevice type), or one STP algorithm per VLAN (perVLAN type). The type of STP algorithm can be selected by setting the ONS 15305> Bridge > SpanningTree > stpTypeAfterReset attribute. The network element must be restarted for the new STP type to become effective.

7.2.1  Configure the STP Algorithm per Device

Use the following steps to configure the STP algorithm per device.

Step 1 Make sure that the STP type is per device (check the ONS 15305 >Bridge > SpanningTree >stpType attribute which indicates the current STP type).

Step 2 Click on the ONS 15305 managed object, and then on the Bridge managed object in the topology browser.

Step 3 Click on the SpanningTree attribute in the attribute window.

Step 4 Set stpEnable to true.

Step 5 Edit the forwardDelay, helloTime, maxAge, and priority attributes if required.

Step 6 Click Save.

Step 7 Click on the SpanningTreePerDevice attribute in the attribute window.

Step 8 Edit the BelongToVLAN attribute as required (if this attribute is set to true, only ports members of a VLAN will participate in the STP algorithm).

Step 9 Click Save.

Step 10 Optionally, the priority, cost, and portEnable attributes can be edited per port. To do so, click on the SpanningTreePort attribute, and modify the attributes as required.

Step 11 Click Save.

7.2.2  Configure the STP Algorithm per VLAN

Use the following steps to configure rhw STP algorithm per VLAN.

Step 1 Make sure that the STP type is perVLA (check the ONS 15305 > Bridge > SpanningTree > stpType attribute which indicates the current STP type).

Step 2 Click the ONS 15305 managed object, and then on the Bridge managed object in the topology browser.

Step 3 Click on the SpanningTree attribute in the attribute window.

Step 4 Set stpEnable to true.

Step 5 Edit the forwardDelay, helloTime, maxAge, and priority attributes if required.

Step 6 Click Save.

Step 7 Click on the SpanningTreePerVLAN attribute in the attribute window.

Step 8 Edit the vlanEnable attribute as required (if this attribute is set to true, the VLAN will run the STP algorithm).

Step 9 Click Save.

Step 10 Optionally, the priority, cost and portEnable attributes can be edited per port for a VLAN. To do so, click on the SpanningTreePerVlanPort attribute belonging to the VLAN, and modify the attributes as required.

Step 11 Click Save.

7.3  Rapid Spanning Tree Protocol Configuration

The original STP uses a long time to recalculate paths after a topology change. Because of the growing use of larger switched networks, this has become a potential reason for performance degradation in certain cases. Rapid STP is one of several attempts to improve on this issue. The ONS15302 and ONS15305 support only a partial RSTP implementation which offers the same type of service as, for example, PortFast on Cisco equipment, because RSTP does not support the actual creation of a spanning tree among the bridges. It will however get the ports facing customers to Forwarding mode without having to wait for 2 x Forwarding delay as is the case with the original STP. The regular STP must be running to prevent loops in network. RSTP is to be used only on ports facing end-user equipment. If the ONS15302 or ONS15305 detects normal STP BPDUs on an interface configured for RSTP it will switch back to normal STP for that interface.

Due to the partial implementation, only the Port-Table and its commands are operational at the first release of the ONS 15302 and the ONS 15305.

7.3.1  Configure RSTP on a Port

Step 1 Click on the ONS 15305 managed object, and then on the Bridge managed object in the topology browser.

Step 2 Click on the RapidSpanningTree attribute, and then on the RapidSpanningTreePort attribute in the attribute window.

Step 3 Identify the (vlanId, port) pair for which the RSTP is to be configured.

Note vlanId is relevant only if the network element is running STP per VLAN. If STP per device is run, RSTP can be enabled per port only, and vlanID is always set to 1.

Step 4 Set the status attribute to true for the selected pair.

Step 5 Click Save.

7.4  MAC Multicast

Multicast is a method of sending one packet to multiple destinations. Multicasting is used for applications such as video conferences, and for distribution of certain information like some routing protocols. A standard IEEE 802.1D bridge will forward multicast frames on all ports that are members of the same VLAN as the port receiving such frames. This might not be desirable if the there is a lot of multicast traffic being transported through a multi-port bridge where the recipients are connected on only one (or a few) of the bridge ports. To alleviate unnecessary bandwidth consumption, the ONS15302 and ONS15305 supports specific tables to control the forwarding of Multicast traffic if desired. Both devices also supports IGMP (Internet Group Management Protocol) snooping which is used to update the multicast tables based on the IGMP messaging between end nodes and IP multicast routers.

Note that multicast traffic will be forwarded as usual if this feature is not enabled; the use of these tables are only necessary for performance tuning.

7.4.1  Configuring MAC Multicast

The Multicast menu has the following menu options:

• IGMPSnooping

• MacMulticastEnable

• MulticastForwardUnregistered.

• MulticastForwarding.

• MulticastForwardingAll.

• MulticastStatic

The parameter MacMulticastEnable is for enabling/disabling of the MAC Multicast control tables.

7.4.1.1  MulticastForwarding

The Forwarding-Table contains multicast filtering information configured into the bridge, or information learned through IGMP Snooping. The Forwarding-Table information specifies the allowed egress ports for a given multicast group address on a specific VLAN, and indicates for which ports (if any) this information has been learnt from IGMP snooping.

VLAN-TAG-ID: Identifies the VLAN to which the filtering information applies.

MULTICAST-ADDRESS: Identifies the destination group MAC address to which the filtering information applies.

EGRESS-PORTS: Indicates the configured egress ports for the specified multicast group address. This does not include ports listed in the Forward All Ports list for this address.

LEARNT: Indicates a subset of ports from the Egress Ports list which were identified by IGMP Snooping and added to the multicast filtering database.

7.4.1.2  MulticastForwardingAll

The Forward-All-Table allows ports in a VLAN to forward all multicast packets.

VLAN-TAG_ID: Identifies the VLAN to which the filtering information applies.

EGRESS-PORTS: Specifies which ports on a VLAN can participate in a Forward Unregistered group. The default setting is all ports.

FORBIDDEN-PORTS: Specifies which ports on a VLAN are restricted from participating in a Forward All group.

STATIC PORTS: Indicates if the egress ports are static or dynamic configured.

7.4.1.3  MulticastForwardUnregistered

The Multicast-Forward-Unregistered-Table defines the behavior of ports regarding forwarding of packets that is not covered by any of the other tables.

VLAN-TAG_ID: Identifies the VLAN to which the filtering information applies.

EGRESS-PORTS: Specifies which ports on a VLAN can participate in a Forward Unregistered group. The default setting is all ports.

FORBIDDEN-PORTS: Specifies which ports on a VLAN are restricted from participating in a Forward Unregistered group.

STATIC PORTS: Indicates if the egress ports are static or dynamic configured.

7.4.1.4  MulticastStatic

The Static-Table contains manually configured filtering information for specific multicast group addresses. This includes information about allowed and forbidden egress ports, and is also reflected in the Forwarding-Table.

VLAN-TAG_ID: Identifies the VLAN to which the filtering information applies.

MULTICAST-ADDRESS: Identifies the destination group MAC address of a frame to which the filtering information applies.

STATIC-EGRESS-PORTS: Indicates a set of ports to which packets received from, and destined to, are always forwarded. This is regardless of the IGMP Snooping setting.

FORBIDDEN-PORTS: Indicates the set of ports to which packets received from and destined to a specific port must not be forwarded. This is regardless of the IGMP Snooping setting.

STATUS:
The possible values are:

Permanent—The table entry is currently in use. When the bridging status is reset this table entry remains in use.

Delete on Reset—This table entry is currently in use. However, when the bridging status is reset the entry is deleted

Delete on Timeout—This table entry is currently in use. However when the bridge times out the entry is deleted.

7.5  Traffic Control

The TrafficControl menu has the following menu options:

• PortPriority

• PriorityGroup

• TrafficClass

7.5.1  PortPriority

BridgePortNumber: a port number identifying a port on the device. For each row, the information in the row applies to the port identified in this column.

DefaultPriority: this is the priority value assigned to frames arriving at this port, when implicit priority determination is used. Any frames arriving at this port, not carrying a priority value in a tag, will get the DefaultPriority value as priority. The value is an IEEE 802.1p priority level. Range is 0 - 7, inclusive.

NumberOfTrafficClasses: gives the number of classes of service - that is, the number of output queues, for the port. All ports on the device will always use 4 queues.

7.5.2  PriorityGroup

BridgePortNumber: a port number identifying one of the on the device. For each row, the information in the row applies to the port identified in this column.

PriorityGroup: indicates which ports are located on the same module, and are thus using the same priority configuration. The ONS 15305 has a teoretical maximum of 65 ports, which are all listed in this table whether or not they are present. PriorityGroup 32 indicates that the port is not present (i.e. the corresponding slot holds a STM-n module which has no Ethernet interfaces).

7.5.3  TrafficClass

Classification of Ethernet frames is done according to the information in the TrafficClass table. The device uses four queues for differentiating traffic; the eight priorities defined by 802.1p must be mapped into those four queues. The default mapping scheme is as recommended by IEEE, but this is configurable by the operator.

Priority Level
Class of Service

6, 7

3

4, 5

2

0, 3

1

1, 2

0


Recommended mapping when using four queues.

BridgePortNumber: a port number identifying one of the on the device. For each row, the information in the row applies to the port identified in this column.

Priority: priority value according to 802.1p. Legal values 0-7.

TrafficClass: indicates which service queue the selected priority value is to be mapped to. Legal values 0-4 (4 is highest priority).

7.6  Manage VLANs

This section explains how to manage a VLAN on the network element.

A network element can be configured to run either VLAN per port or VLAN per port and per protocol.

The section also involves management of the complete life cycle of a VLAN, including:

•Creation, presentation, modification, and deletion of a VLAN.

•Creation, presentation, modification, and deletion of an Ethernet User Defined Protocol.

•Presentation and modification of Generic Attribute Registration Protocol VLAN Registration Protocol (GVRP).

7.6.1  Virtual Local Area Networks (VLAN)

A LAN consists of a number of computers that share a common communication line within a small geographical area. A Virtual LAN is a LAN where the grouping of computers are based on logical connections, for example by type of users, by department etc. It is easier than for a physical LAN to add and delete computers to/from a VLAN and to manage load balancing. The management system relates the virtual picture and the physical picture of the network.

The network element supports two types of VLAN

•Per port

•Per port and protocol

Both types of VLANs cannot be run simultaneously on the network element, that means either all VLANs per port or all per port and per protocol. The protocol can either be one from a set of predefined protocols or from Ethernet protocols defined by you. Different Ethernet protocol types can be IP, IPX, Appletalk, etc.

The number of Ethernet-ports in ONS15305 which can be assigned to a VLAN, is limited to 64. The maximum number of Ethernet-ports per slot is 16.See also the "Question 7" section on page A-2.

There are three steps involved in the definition of VLAN on the network element.

•A common VLAN type is defined for the Bridge.

•A set of common parameters for a new VLAN is defined.

•New ports can be added to a VLAN.

It is assumed you have the appropriate rights to perform management operations.

7.6.2  Tagged/Untagged LAN Ports

In order to transport traffic from multiple VLANs over the same LAN port (from one bridge to another) the Ethernet frames must be tagged according to what VLAN they belong to, so that the connected bridge knows what frames are to be forwarded into which VLAN (This is according to the IEEE spec 802.1Q). This is done by inserting four bytes into the Ethernet frame header, with information about the VLAN ID (VID) the frame is associated with. The VID of a specific VLAN is defined at the time the VLAN is created. This tagging can be enabled for each port in a VLAN. This is, however, only used for communication between bridges (and in some cases VLAN aware servers), and not on ports facing regular end user network equipment. A LAN port operating in untagged mode will discard tagged frames on ingress. LAN ports operating in tagged mode will only accept frames tagged in accordance with the VID of the VLAN(s) of wich the port is a member.

For example, if a port is member of two VLANs with the VIDs of 10 and 20, and the port receives frames tagged according to VID 10, 20 and 30, only the frames with VID 10 and 20 will be accepted and forwarded. The frames with VID 30 will be discarded.

It is possible to have a VLAN where some of the member ports are tagged while others are not. As long as there is traffic from only one VLAN passing through a port, there is no need to enable tagging.

7.7  VLAN Provisioning

Cisco Edge Craft has a custom GUI for VLAN provisioning ( Figure 7-4). The VLAN GUI makes VLAN related configuration easier for the user by grouping together a number of managed objects and attributes under a unique GUI.

Figure 7-4 VLAN GUI - Overview

.

The following examples show how a VLAN perport and per protocol can be created and provisioned by using the custom GUI. The VLAN custom GUI can be opened either by clicking on VLAN Setting under the Bridge menu on the Cisco Edge Craft desktop, or by right-clicking on Bridge MO in the topology browserand then selecting VLAN Setting.

7.7.1  Configure a New VLAN Per Port

Use the following steps to create a new VLAN per port.

Step 1 Verify that the VLAN type on the top right corner of the GUI is set to perPort ( Figure 7-5). If not, set VLAN type to perPort and click Yes when asked if the network element should be rebooted.

Figure 7-5 VLAN Settings

Step 2 Click Add in the GUI ( Figure 7-6).

Figure 7-6 Add a VLAN

.

Step 3 The GUI suggests default values for all the attributes. Edit the description, tag, and/or addressType attributes if required ( Figure 7-7).

Figure 7-7 Set VLAN Attributes

.

Step 4 Click Save.

7.7.2  Configure a New VLAN Per Protocol and Per Port

Use the following steps to create a new VLAN per protocol and per port.

Step 1 Verify that the VLAN type on the top right corner of the GUI is set to perProtAndPort. If not, set VLAN type to perProtAndPort, and click Save. The network element must be restarted before the change is effective.

Step 2 Click Add on the GUI, Figure 7-8.

Figure 7-8 Add a VLAN

Step 3 Edit the protocolType and protocol attributes to indicate which protocol will be used to determine the VLAN membership of a packet. The user can choose between nine pre-defined protocols, and one Ethernet user defined protocol.

Figure 7-9 Configure a VLAN

.

Note If protocolType is set to notUsed, and protocol to zero, a VLAN per port is basically defined, that means the protocol carried by a packet does not influence its membership in a VLAN.

7.7.3  Configure an Ethernet User Defined Protocol

7.7.3.1  Use the Ethernet User Defined Protocol

The ethernetDefinedProtocol attribute allows you to define a non-predefined protocol based on the etherType field of Ethernet frames. This user-defined protocol is further used to create protocol-based VLANs ( Figure 7-10).

Step 1 Select VLAN Settings from the Bridge menu.

Step 2 Click Ethernets in the content pane.

Figure 7-10 Configuration of an Ethernet User Defined Protocol

.

Step 3 Click Add on the toolbar (if no protocol is already defined). If a protocol is already defined, both fields described in Step 4 can be directly edited.

Step 4 Set the EthernetType attribute to the value of the EtherType indicating the required protocol. The ProtocolName attribute can optionally be used to give a user-friendly name to the protocol.

Step 5 Click Save on the toolbar.

Note The EtherType numbers are maintained by the internet assigned numbers authority (IANA), and can be accessed on the Web at the following address: http://www.iana.org/assignments/ethernet-numbers.

Assuming that a user wants to define a VLAN based on the address resolution protocol (ARP), the ethernetType must be set to 0806 (in hex), and the protocolName attribute could be, for example set to ARP to identify the protocol.

The Ethernet user defined protocol is relevant only when the network element runs VLAN per protocol and port.
Maximum one Ethernet user defined protocol can be currently defined on the network element.
To use the Ethernet user defined protocol as a VLAN protocol for a particular VLAN, set the protocolType attribute under Bridge > VLAN to ethUserDefined. The protocol attribute under Bridge > VLAN, which is used to identify a specific protocol, must then always be set to 1, since there is maximum one Ethernet user defined protocol.

7.7.3.2  Use Pre-defined Protocols

Step 1 Set protocolType to preDefined.

Step 2 Set protocol to 1 for other, that means the VLAN will include any protocol except the one specified in Table 7-1.

.

Table 7-1 VLAN Protocol

2

for IP protocol

4

for IPX Raw protocol

5

for IPX Ethernet protocol

6

for IPX LLC protocol

7

for IPX SNAP protocol

8

for DECNET protocol

10

for NETBIOS protocol

13

for SNA protocol


Step 3 Edit the description, tag, and/or addressType attributes if required.

Step 4 Click Save.

7.7.4  Configure VLAN Port members

Use the following steps to add port members to an existing VLAN.

Step 1 Select the VLAN to which ports will be added. The VLAN is highlighted in the virtual local area network window (top window in Figure 7-11). The list of ports already members of the VLAN is displayed in the VLAN ports window (bottom window in Figure 7-11).

Figure 7-11 Configuration of VLAN Port members

.

Step 2 Activate the VLAN ports window by clicking anywhere in the window. The color of the title bar for the VLAN ports window changes to blue to indicate that the window is selected.

Step 3 Click Add.

Step 4 Edit the bridgePortNumber attribute. The attribute is displayed as slot/port (bridgePortNumber) and can be entered by the user as slot/port or bridgePortNumber (the system will update the display automatically).

Note The value of bridgePortNumber for LAN and WAN ports can be found under the LAN and WAN managed objects respectively.

Figure 7-12 Edit the Bridge Port Number

Step 5 Edit the tagging and forbiddenEgressPort attributes if required.

Step 6 Click Save.

7.7.5  GVRP

Use the following steps to modify GARP VLAN registration protocol (GVRP).

Step 1 Click GVRP in the Content pane ( Figure 7-13).

Figure 7-13 GVRP Attributes

.

Step 2 Edit the following attributes as needed:

•PortEnable

Set to enabled or disabled.

•JointTime

Set value in centiseconds.

•LeaveTime

Set value in centiseconds.

•LeaveAllTime

Set value in centiseconds.

Step 3 To view legal time values, click in an attribute cell and focus the mouse pointer over the cell. A tooltip will display legal value range for the selected attribute ( Figure 7-14).

Figure 7-14 Select Legal Time Values

.

7.8  Examples

This section provides examples for configuring an IP interface, configuring a static route, and configuring an RIP filter.

7.8.1  Configuration of an IP Interface

An IP interface can be created only for a physical port, a management interface, or a VLAN (port based VLAN or IP-based VLAN only).

The following steps configure an IP interface with an IP address ( Figure 7-15).

Step 1 Click on the ONS 15305 managed object, and then the ip managed object in the topology browser.

Step 2 Double-click on IpInterface in the attributes window.

Step 3 Click Add on the toolbar.

Figure 7-15 Configuration of an IP Interface

.

Step 4 The following attributes have no default values, and must therefore be defined:

•interfaceIpAddress

set the IP address according to your addressing plan.

•interfaceNetworkMask

set the network mask according to your addressing plan.

•interfaceNumber

the interface number. An IP interface can be defined for a LAN port, a WAN port, the management port, a DCC running IP or a VLAN. The interface number corresponding to these objects is specified by the ifIndex attribute present under their respective M.O.

Step 5 Click Save on the toolbar.

Note One interface (identified by a specific ifIndex) can be allocated several IP addresses. This enables the user to connect the interface to a network segment where multiple subnets are defined.
IP addresses and network masks associated with the management interfaces, that means the management port, and the DCC can also be edited via the management interfaces M.O.

7.8.2  Configuration of a Static Route

An IP static route is a route defined by the user through the management system. Such a route does not age out, and will stay in the network element routing table as long as it is not explicitly deleted by the user. As any other route, a static route is active, and therefore included in the forwarding table provided that the interface associated with the route is up.

Note The forwarding table is a subset of the routing table. It contains only the active routes, that means routes being used by the network element to forward IP datagrams. Typically, a route becomes inactive, and is removed form the forwarding table when the operational status of its associated interface is down. Only the forwarding table is visible in the Cisco Edge Craft via the ipRoute attribute.

7.8.2.1  Create a Static Route

Step 1 Click on the ONS 15305 managed object, and then on the IP managed object in the topology browser, Figure 7-16.

Step 2 Double click on the ipRoute attribute in the attributes window.

Step 3 Click Add on the toolbar.

Figure 7-16 Create a Static Route

.

Step 4 Set the destinationIpAddress, destinationNetworkMask, nextHop, interfaceNumber attributes.

Step 5 Set the routeType attribute to either Remote if the route is meant to forward traffic, or Reject if the route is meant to discard traffic for the specified destination.

Step 6 Optionally, one or more metric attributes can be set. Metrics are used by the routing process to select a preferential route (the route with the lowest metric) if there are several possible routes for a given destination.

Step 7 Click Save on the toolbar.

Note The value x set to the destinationNetworkMask attribute will be rejected by the network element if the bitwise logical-and of x with the value of the destinationIpAddress attribute is not equal to the value of the destinationIpAddress attribute.
The IP address of the next router en route specified by the next-hop attribute must be directly reachable via the interface specified by the interfaceNumber attribute, that means the next-hop IP address must belong to the (one of the) subnet(s) defined for the interface identified by the interfaceNumber attribute.

7.8.2.2  Static Route Example

To define a static route to the subnet 10.10.0.0 in router R1 ( Figure 7-17).

Figure 7-17 Figure - Static Route in Router R1

Step 1 Set destinationIpAddress: 10.10.0.0

Step 2 Set destinationNetworkMask: 255.255.0.0

Step 3 Set nextHop: 20.20.20.1 (one must choose the IP address of router R2 which lies on the same subnet as the interface identified by the interfaceNumber attribute in R1)

Step 4 Set interfaceNumber: ifIndex associated with interface A.

Step 5 Set routeType: Remote

Step 6 Set metric: 1

7.8.2.3  Configuration of a Default Route

A default route is a particular static route which is used to by the network element to send all the traffic for which no other routing information exists. If no default route has been defined, and no specific routing information exists for an IP datagrams requesting forwarding, the datagram is discarded.

The default route is created by setting both the destinationIpAddress and the destinationNetworkMask attributes to 0.0.0.0. The router identified by the next-hop attribute is then referred to as default router, also know as default gateway.

Note There exists only one active default route in the network element. The default gateway can also be edited via the Management Interfaces M.O.

7.8.2.4  Default Route Example

To create a default route on router R1 using router R2 as default gateway ( Figure 7-17).

Step 1 Set the destinationIpAddress: 0.0.0.0

Step 2 Set the destinationNetworkMask: 0.0.0.0

Step 3 Set the nextHop: 20.20.20.1

Step 4 Set interfaceNumber: ifIndex associated with interface 'A'.

Step 5 Set routeType: Remote

Step 6 Set metric: 1

7.8.3  Configuration of a RIP Filter

An IP RIP filter allows the user to control the propagation of RIP routing information, and eventually to modify the RIP routing by filtering out information about specific routes. In addition, IP RIP filters help reducing the size of the RIP table allowing for a faster table look-up, and releasing memory for other processes.

7.8.3.1  Create an IP RIP Global Filter

Step 1 Click on the ONS 15305 or ONS 15302 managed object, and then on the IP managed object in the topology browser.

Step 2 Double click on the rip attribute in the attributes window.

Step 3 Double click on the ripGlobalFilter attribute in the attributes window.

Step 4 Click Add on the toolbar.

Step 5 Set the type, networkAddress, numberOfMatchBits, and filterAction attributes.

Step 6 Click Save on the toolbar.

7.8.3.2  IP RIP Global Filter Examples

To define a RIP global filter that prevents the network element from advertising any route to the subnet 10.10.0.0, enter the following filter:

Type: output

NetworkAddress: 10.10.0.0

NumberOfMatchBits: 16

FilterAction: Deny

To define a RIP interface filter which prevents the network element from accepting routes for the subnet 192.168.0.0, but still accepts routes for the subnet 192.1680.1.0, enter the following two filters:

#1: Type: input

NetworkAddress: 192.168.0.0

NumberOfMatchBits: 16

FilterAction: Deny

#2: Type: input

NetworkAddress: 192.168.1.0

NumberOfMatchBits: 24

FilterAction: Permit

Note The procedure to define a RIP interface filter is identical to the procedure described above. A RIP interface filter applies only to a specific interface (specified by the ripInterface attribute) instead of applying to every RIP-enabled interface on the network element.
RIP interface filters take precedence over RIP global filters.

7.9  Open Shortest Path First

The open shortest path first (OSPF) is a link state routing protocol (unlike RIP which is distance vector routing protocol). Configuring the network element to run OSPF can be performed through three basic steps:

Step 1 Configure one or several OSPF areas.

Step 2 Configuring the OSPF interfaces.

Step 3 Enable OSPF on the network element.

7.9.1  Supported OSPF Areas: Transit and Stub Areas

Three OPSF area types are currently defined by the standards:

•Transit areas (including the backbone area 0.0.0.0) defined in OSPF version 2 (RFC2328). Transit areas accept intra-area, inter-area, and external routes.

•Stub areas defined in OSPF version 2 (RFC2328). Stub areas come in two flavours: they can either accept intra-area, inter-area, and default routes, or only intra-area and default routes. Stub areas which propagate only intra-area and default routes within the area are sometimes referred to as totally-stub areas.

•Not-so-stubby areas (NSSA) defined in OSPF NSSA option (RFC1587). NSSAs are a hybrid between transit and stub areas. They can import a few external routes into the area via an autonomous system border router (ASBR) present in the area.

The network element currently supports only transit and stub areas. In addition, it is currently not possible to configure a stub area to import only intra-are and default routes, tha means it is not possible to configure an area as a totally-stub area.

7.9.2  Configure an OSPF Area

Use the following steps to configure a new OSPF area.

Step 1 Click on the ONS 15305 or ONS 15302 managed object, and then on the IP managed object in the topology browser.

Step 2 Click on the OSPF attribute, and then on the OspfArea attribute in the attribute window.

Step 3 Click Add.

Step 4 Set the areaID attribute.

Step 5 Set the importAsExternal and metric attributes as required.

Step 6 Click Save.

Note Setting the importAsExternal attribute to importAsExternal define a transit area, while setting the importAsExternal attribute to importNoExternal define a stub area.

Note The metric attribute is only relevant for stub areas, that means when the attribute importAsExternal is set to importNoExternal.

7.9.3  Configure an OSPF Interface

Use the following steps to configure an OSPF interface.

Step 1 Click on the ONS 15305 or ONS 15302 managed object, and then on the IP managed object in the topology browser.

Step 2 Click on the OSPF attribute, and then on the OspfInterface attribute in the attribute window.

Step 3 Identify the OSPF interface to configure via its IP address listed under the interfaceIpAddress attribute.

Step 4 Set the areaId attribute to the area to which you want to attach the interface. Note that the area must have been previously defined; see the "Configure an OSPF Area" section.

Step 5 Set the interfaceType attribute to the required type, and make sure that the ospfEnable attribute is set to Enabled (this is the default value).

Step 6 Edit the helloInterval, metricValue, authentificationType, authentificationKey, transitDelay, routerDeadInterval, pollInterval, retransmissionInterval, and priority attributes if required.

Step 7 Click Save.

7.9.4  Enable OSPF on the Network Element

Use the following steps to enable OSPF globally.

Step 1 Click on the ONS 15305 or ONS 15302 managed object, and then on the IP managed object in the topology browser.

Step 2 Click on the OSPF attribute in the attribute window.

Step 3 Set the ospfEnable attribute to enabled.

Step 4 Click Save.

7.10  DHCP

The network element can be configured as a DHCP server (ONS 15305 > IP >DHCP >dhcpServerEnable set to enable) or as a DHCP relay (ONS 15305> IP > DHCP > dhcpServerEnable set to disable).

If the network element is configured to relay DHCP requests, the IP address of the next DHCP server must be configured by setting the ONS 15305 > IP > DHCP > nextServerIpAddress attribute.

If the network element is configured as a DHCP server, the user can configure the ranges of available IP addresses for every IP interface on the network element; see the "Configure the Range of IP Addresses for the DHCP Server" section. In addition, by using DHCP manual allocation mechanism, the user can define the IP address to be allocated to a host based on its MAC address and optionally its name; see the "Configure the DHCP Server for Manual Allocation" section.

7.10.1  Configure the Range of IP Addresses for the DHCP Server

Use the following steps to configure the range of IP addresses

Step 1 Click on the ONS 15305 managed object, and then on the IP managed object in the topology browser.

Step 2 Click on the DHCP attribute, and then on the dhcpAddressRange attribute in the attribute window.

Step 3 Click Add.

Step 4 Set the interfaceIpAddress attribute to the IP address of the network element on which the range of IP address shall be available.

Step 5 Set the ipAddressFrom and ipAddressTo attributes to the first and the last IP address allocated for the range respectively.

Step 6 Edit the leaseTime, defaultRouter, and probeEnable attributes as required.

Step 7 Click Save.

Note The range of available IP addresses [ipAddressFrom; ipAddressTo] must be on the same subnet as the IP address of the interface (interfaceIpAddress) on which the range applies.
If you want to allocate IP address permanently, that means to use the automatic allocation mode of DHCP, the leaseTime attribute must be set to -1.

7.10.1.1  Configure the DHCP Server for Manual Allocation

Configure an IP address for manual allocation

Step 1 Click on the ONS 15305 managed object, and then on the IP managed object in the topology browser.

Step 2 Click on the DHCP attribute, and then on the dhcpAllocation attribute in the attribute window.

Step 3 Click Add.

Step 4 Set the ipAddress attribute to the IP address to be allocated via the manual allocation mode of DHCP.

Step 5 Set the mechanism attribute to manual.

Step 6 Edit the macAddress, hostName, defaultRouter, configurationServerIpAddress, and configurationFileName attributes as required.

Step 7 Click Save.

Note To match any incoming MAC address, the macAddress attribute must be to "00:00:00:00:00:00".

hometocprevnextglossaryfeedbacksearchhelp

Posted: Fri Sep 14 11:39:52 PDT 2007
All contents are Copyright © 1992--2007 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.