IP Addressing issues

IP Addressing issues 

P Addressing issues

Sample Network Topology

To address IP issues, ensure that the ONS 15454 is configured correctly, and that IP addresses are visible on the PC. Use the ping and tracert commands to verify connectivity between the PC and the ONS 15454.


Link-Level Connectivity

The network utilizes two types of Ethernet cables: straight-through and crossover. Use the following guidelines to determine which cable type to use between network devices:

The sample network uses two types of Ethernet cable, namely, straight-through and crossover. This table enables you to verify which type of Ethernet cable to use between the various network connections:

 

TCC

Wire wrapped backplane pins

PC or Workstation

Straight through cable

A1

RJ-45 pin 2

B1

RJ-45 pin 1

A2

RJ-45 pin 6

Router

B2

RJ-45 pin 3

Hub or Switch

Cross over cable

A1

RJ-45 pin 6

B1

RJ-45 pin 3

A2

RJ-45 pin 2

B2

RJ-45 pin 1

 

Straight-through Cable:

Connections:

PC or Workstation to Router/Hub/Switch:

Pin 1 (PC) connects to Pin 1 (Router/Hub/Switch)

Pin 2 (PC) connects to Pin 2 (Router/Hub/Switch)

Pin 6 (PC) connects to Pin 6 (Router/Hub/Switch)

Pin 3 (PC) connects to Pin 3 (Router/Hub/Switch)


Crossover Cable:

Connections:

PC to PC or Hub to Hub/Switch to Switch:

Pin 1 (PC) connects to Pin 3 (Other PC/Hub/Switch)

Pin 2 (PC) connects to Pin 6 (Other PC/Hub/Switch)

Pin 6 (PC) connects to Pin 1 (Other PC/Hub/Switch)

Pin 3 (PC) connects to Pin 2 (Other PC/Hub/Switch)


Troubleshooting Link-Level Connectivity

If issues arise with link-level connectivity:

  • Faulty Cable: Inspect the cable for damage and replace if necessary.
  • Incorrect Cable or Pinouts: Confirm that you are using the correct type of cable and pin configuration.
  • Faulty Port: Test another port on the TCC, PC, hub, or router.
  • Speed or Duplex Mismatch: Ensure that settings match. For instance, the TCC Ethernet port should be set to 10baseT half-duplex.


IP-Level Connectivity

The ONS 15454 allows for up to 16 static routes to enable IP connectivity to remote CTC workstations via routers. Configure these static routes using the CTC interface.


Note: Version 2.2.x of the CTC software supports up to four concurrent sessions per node, while version 3.x and later support up to five. Performance can vary based on activity levels and network conditions.


To set up static routes:

  • Navigate to the Provisioning > Network tabs in the CTC interface.
  • Click Create in the Static Routes panel.
  • Enter the destination IP address and route details.


For example:

  • CTC Workstation IP Address: 144.254.14.38 (Class B network, 16-bit subnet mask)
  • 15454 IP Address: 10.200.100.11 (Class A network, 8-bit subnet mask)
  • Router-C IP Address: 10.200.100.5 (on the same segment as the 15454)


Troubleshooting the 15454

If you encounter issues when configuring static routes:

  • Incorrect IP Address/Subnet Mask: Ensure all interfaces on the same network are within the same subnet to communicate directly.
  • Duplicate IP Addresses: Verify that each IP address is unique within its network.
  • Incorrect/Missing Default Gateway: Set the default router on the 15454 to the adjacent router’s Ethernet IP address.
  • Missing Static Routes: Ensure the static route is correctly configured and distributed to all relevant nodes.


Understanding the 15454 Routing Table

In a ring network topology, interconnected 15454 elements form an Open Shortest Path First (OSPF) area. Nodes use SONET Data Communication Channel (DCC) links to exchange routing information.


Note: The static route configured on one node will be advertised to all other nodes in the ring.


Troubleshooting the 15454 Routing Table

Common SDCC connectivity issues include:

  • Misconfigured SDCC Terminations: Ensure correct SDCC configuration. Avoid changing area IDs or disabling OSPF on the SDCC unless necessary.
  • Fiber Path Issues: Check for Loss of Signal (LOS) or Loss of Frame (LOF) alarms.
  • Unconfigured SDCC Tunnels: Ensure SDCC tunnels are properly configured.


Configuring the Router

For a network with a four-node Bi-Directional Line Switch Ring (BLSR):

Router Configuration Example:

! hostname Router-C

! . . 

interface Ethernet0

 ip address 10.200.100.5 255.0.0.0

! 

interface Ethernet1

 ip address 144.254.14.37 255.255.0.0

! . .

ip route 11.200.100.12 255.255.255.255 10.200.100.11

ip route 12.200.100.13 255.255.255.255 10.200.100.11

ip route 13.200.100.14 255.255.255.255 10.200.100.11

! . .

line con 0

 exec-timeout 0 0

 password 7 131200

 login

line aux 0

line vty 0 4

 password 7 010411

 login

! end


Router-C Configuration:

Router-C must be configured to include static routes for nodes not directly connected. From Cisco ONS15454 Release 3.3 onwards, the Proxy Server feature can simplify this by allowing the Gateway ONS15454 to act as a proxy for all nodes behind it.


Troubleshooting the Router

To troubleshoot router issues:

  • Verify IP Connectivity: Ensure connectivity between CTC workstations and 15454 gateway nodes.
  • Check Router Forwarding Tables: Ensure routers have entries for the IP subnets of both CTC workstations and 15454 gateway nodes.
  • Perform Ping Tests: Use ping commands to test connectivity and verify configurations.
  • Configure Static Routes: Ensure static routes are set up for non-gateway 15454 nodes.


Note: In networks using Proxy Server features, ensure the ping application supports SOCKS V5.

 For Support