Configure Ip Routing; Application Protocols; Ftp - Nortel Optical Multiservice Edge 6130 Planning Manual

•
Auto GRE implementation rules
You must observe the following rules when you implement Auto GRE:
•
•
•

Configure IP routing

Configure the interface to use either static or dynamic routing scheme. Refer
to IP communication on page 10-11

Application protocols

This section lists out the supported application protocols and commands which
can be useful while working and troubleshooting an OME6130 network
element.

ftp

TCP/IP File transfer protocol (FTP) is a standard application layer protocol
used for transferring files across a network. This protocol uses a client/server
architecture. Both the FTP client and server are enabled on the OME6130. The
OME6130 supports active FTP.
The FTP protocol is used mainly during firmware, software, or on-line
documentation upgrade to handle all file transfers between the source (server)
of the image files and the network elements (clients). The FTP protocol is also
used for database backup and restore operations.
Provision the NSAP Selector Byte of the tunnel destination node. Use
hexadecimal 2F (47 in decimal) for GRE protocol.
Note: When provisioning a static GRE tunnel between the OME6130 and
OME6500, a mismatch of the NSAP selector bytes provisioned at the
OME6500 and the OME6130 is expected. The NSAP Selector Byte
provisioned at the OME6130 WUI should be set to 2F, and the network
selector (NSEL, last 2 bytes of NSAP) provisioned from the OME6500
craft interface must be set to 00. The OME6500 automatically sets the
NSEL internally to support the required transport service.
Rule 1: The default route of 0.0.0.0/0 should not be configured over the
LAN port (eth0) and should not be advertised over iISIS on the GNE. This
route may interfere with the static route that needs to be configured on the
AGRE interface on every OME6130 network element.
Rule 2: On all OME6130 network elements (GNE and remote NEs), it is
recommended to manually provision a non-advertised static route for the
AGRE to be within the network element DCN subnet.
Rule 3: On all remote network elements, in addition to the manually
provisioned static route in Rule 2, a non-advertised default route of
0.0.0.0/0 must also be provisioned over the AGRE interface.
Planning Guide NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Appendix A: Data communications planning 10-21
for more details.