Understanding INE Logical Topology and configuration.

We will be doing the base configuration for INE Topology for CCIE RnS. If you haven’t purchase INE workbooks, go for it. Its really worth .

Below is the logical topology. Image

 

I am using the Web IOU for configuring it. I have connected to all the devices, did bring up all the ports and configured hostnames only.

We will draw the diagram based on the outputs.

Note : This also helps a lot in real time customer’s network as most of the customer’s do not have the network diagram updated.

We will execute the command show cdp neighbors on all devices and will draw the diagram.

Rack1SW1#show cdp nei
Capability Codes: R – Router, T – Trans Bridge, B – Source Route Bridge
S – Switch, H – Host, I – IGMP, r – Repeater, P – Phone,
D – Remote, C – CVTA, M – Two-port Mac Relay

Device ID        Local Intrfce     Holdtme    Capability  Platform  Port ID
Rack1SW4         Eth 4/0           137              R S   Linux Uni Eth 2/0
Rack1SW4         Eth 4/1           137              R S   Linux Uni Eth 2/1
Rack1SW4         Eth 4/2           137              R S   Linux Uni Eth 2/2
Rack1SW2         Eth 2/0           137              R S   Linux Uni Eth 2/0
Rack1SW2         Eth 2/1           137              R S   Linux Uni Eth 2/1
Rack1SW2         Eth 2/2           137              R S   Linux Uni Eth 2/2
Rack1SW3         Eth 3/0           137              R S   Linux Uni Eth 2/0
Rack1SW3         Eth 3/1           137              R S   Linux Uni Eth 2/1
Rack1SW3         Eth 3/2           137              R S   Linux Uni Eth 2/2
Rack1R1          Eth 0/1           171               R    Linux Uni Eth 0/0
Rack1R3          Eth 0/3           173               R    Linux Uni Eth 0/0
Rack1R5          Eth 1/1           177               R    Linux Uni Eth 0/0

The above output is execute on Switch 1. The Device ID shows the host-name of the neighboring device. Local Interface refers to the port on the device where the command was executed. In this example it is switch 1. Port ID refers to the neighboring device port.

Looking at the first 3 line, it says Switch1 is connected to Switch 4 via ethernet 4/0,e4/1,e4/2.

||SW-1||–e4/0————-e2/0–||Sw4||

||SW-1||–e4/1————-e2/1–||Sw4||

||SW-1||–e4/2————-e2/2–||Sw4||

Similarly,

||SW-1||–e2/0————-e2/0–||Sw2||

||SW-1||–e2/1————-e2/1–||Sw2||

||SW-1||–e2/2————-e2/2–||Sw2||

and

||SW-1||–e3/0————-e2/0–||Sw3||

||SW-1||–e3/1————-e2/1–||Sw3||

||SW-1||–e3/2————-e2/2–||Sw3||

So in Total we have 9 links from SW1 to other switches respectively. These 9 links would be configured as Trunk because we want the many vlans to be travel across these links.

We also have 3 links connecting to Routers R1,R3 and R5 via e0/1,e0/3 and e0/5 to their e0/0 ports.

||SW-1||–e0/1————-e0/0–||R1||

||SW-1||–e0/3————-e0/0–||R3||

||SW-1||–e0/5————-e0/0–||R5||

Similarly you can draw the complete the diagram following the above. I have pasted the outputs from SW2,SW3 and SW4 respectively.

Rack1SW2#show cdp nei
Capability Codes: R – Router, T – Trans Bridge, B – Source Route Bridge
S – Switch, H – Host, I – IGMP, r – Repeater, P – Phone,
D – Remote, C – CVTA, M – Two-port Mac Relay

Device ID        Local Intrfce     Holdtme    Capability  Platform  Port ID
BB2              Eth 0/0           167               R    Linux Uni Eth 0/0
Rack1SW4         Eth 4/0           165              R S   Linux Uni Eth 3/0
Rack1SW4         Eth 4/1           165              R S   Linux Uni Eth 3/1
Rack1SW4         Eth 4/2           165              R S   Linux Uni Eth 3/2
Rack1SW3         Eth 3/2           165              R S   Linux Uni Eth 3/2
Rack1SW3         Eth 3/1           165              R S   Linux Uni Eth 3/1
Rack1SW3         Eth 3/0           165              R S   Linux Uni Eth 3/0
Rack1SW1         Eth 2/1           165              R S   Linux Uni Eth 2/1
Rack1SW1         Eth 2/2           165              R S   Linux Uni Eth 2/2
Rack1SW1         Eth 2/0           165              R S   Linux Uni Eth 2/0
Rack1R2          Eth 0/2           158               R    Linux Uni Eth 0/0
Rack1R4          Eth 1/0           140               R    Linux Uni Eth 0/0
Rack1R6          Eth 1/2           132               R    Linux Uni Eth 0/0

Rack1SW3#show cdp nei
Capability Codes: R – Router, T – Trans Bridge, B – Source Route Bridge
S – Switch, H – Host, I – IGMP, r – Repeater, P – Phone,
D – Remote, C – CVTA, M – Two-port Mac Relay

Device ID        Local Intrfce     Holdtme    Capability  Platform  Port ID
BB3              Eth 0/0           131               R    Linux Uni Eth 0/0
Rack1SW4         Eth 4/0           150              R S   Linux Uni Eth 4/0
Rack1SW4         Eth 4/1           150              R S   Linux Uni Eth 4/1
Rack1SW4         Eth 4/2           150              R S   Linux Uni Eth 4/2
Rack1SW2         Eth 3/2           150              R S   Linux Uni Eth 3/2
Rack1SW2         Eth 3/1           150              R S   Linux Uni Eth 3/1
Rack1SW2         Eth 3/0           150              R S   Linux Uni Eth 3/0
Rack1SW1         Eth 2/2           150              R S   Linux Uni Eth 3/2
Rack1SW1         Eth 2/1           150              R S   Linux Uni Eth 3/1
Rack1SW1         Eth 2/0           150              R S   Linux Uni Eth 3/0
Rack1R5          Eth 1/1           148               R    Linux Uni Eth 0/1

Rack1SW4#show cdp nei
Capability Codes: R – Router, T – Trans Bridge, B – Source Route Bridge
S – Switch, H – Host, I – IGMP, r – Repeater, P – Phone,
D – Remote, C – CVTA, M – Two-port Mac Relay

Device ID        Local Intrfce     Holdtme    Capability  Platform  Port ID
Rack1SW2         Eth 3/1           144              R S   Linux Uni Eth 4/1
Rack1SW2         Eth 3/2           144              R S   Linux Uni Eth 4/2
Rack1SW2         Eth 3/0           144              R S   Linux Uni Eth 4/0
Rack1SW3         Eth 4/0           144              R S   Linux Uni Eth 4/0
Rack1SW3         Eth 4/1           144              R S   Linux Uni Eth 4/1
Rack1SW3         Eth 4/2           144              R S   Linux Uni Eth 4/2
Rack1SW1         Eth 2/2           144              R S   Linux Uni Eth 4/2
Rack1SW1         Eth 2/1           144              R S   Linux Uni Eth 4/1
Rack1SW1         Eth 2/0           144              R S   Linux Uni Eth 4/0
Rack1R4          Eth 1/0           176               R    Linux Uni Eth 0/1

The resulting diagram would be referred as Physical Diagram. See Below :I made this diagram using GNS3.Image

Comparing it with the logical diagram we see that  R1 E0/0 should be part of VLAN 146. So port E0/1 on SW1 should be an access port and member of VLAN 146. Traffic comming on port E0/1 on SW1 would be tagged as VLAN 146.

On SW1 we also have R5 0/0 connected to port E0/5. As per logical Diagram this should be in VLAN 5.

Port 0/3 on SW1 is a Routed Port. Hence we need to issue no switchport command under the interface and assign an IP address.

 

we see that R1 e0/0, R4 e0/1 and R6 e0/0  are part of VLAN 146.

So looking at the physical connections we just made, we see that on SW1 port e0/1 should be part of VLAN 146, SW4 E1/0 and SW2 e1/2 should be access ports belonging to VLAN 146.

There’s is a Catch!!! Watch closely…In the logical Diagram R6 E0/0 has 2 sub interface and these sub interfaces are in 2 different VLANS 🙂

That’s a Router ON a Staick Concept!!.

Its Simple :

On R6 :

int e0/0

no shutdown

exit

int e0/0.146 =====>Sub Interface number can be anything. We just give 146 here which is matching our Vlan number.

encapsulation dot1q 146

ip add 155.1.146.1 255.255.255.0

no shut

exit

int e0/0.67

encapsulation dot1q 67

ip add 155.1.67.6 255.255.255.0

no shut

exit

Sw1 E1/2 connects to R6 E0/0. Earlier we configured E1/2 as member of VLAN 146. Now we see that from the same interface we are receiving tagged packets i.e vlan 146 and Vlan 67. Hence this port should be TRUNK port.

On All Switches, we have ports E2/0-2, E3/0-2,E4/0-2 connecting to other switches. As a result we will be configuring these ports as Trunk Ports.

ON ALL Switches :

conf t

int range E2/0-2, E3/0-2,E4/0-2

Shutdown

exit

conf t

int range E2/0-2, E3/0-2,E4/0-2

Switchport trunk encap dot1q  ————-> Using Dot1q encapsulation as ISL does not work on IOU.

switchport mode trunk ——> Hard Coding to be as  Trunk ports.

exit

and on SW1

int e1/2

Switchport trunk encap dot1q

switchport mode trunk

exit

conf t

int range E2/0-2, E3/0-2,E4/0-2

No Shutdown

exit

Total VLANS used in this network topology : VLan 5,7,8,9,10,22,43,58,67,79,146
We will configure all these vlans on all the Switches.

On ALL SWITCHES:

en

conf t

Vlan 5,7,8,9,10,22,43,58,67,79,146

exit

Vlan Port configuration :SO

Some output Omitted

SW1#sh run int e1/1

interface Ethernet1/1
switchport access vlan 58
switchport mode access
duplex auto
spanning-tree portfast
end

Rack1SW1#sh run int e0/1

interface Ethernet0/1
switchport access vlan 146
switchport mode access
duplex auto
spanning-tree portfast
end

Rack1SW2#sh run int e0/0
!
interface Ethernet0/0
switchport access vlan 22
switchport mode access
duplex auto
spanning-tree portfast
end

Rack1SW2#sh run int e0/2

!
interface Ethernet0/2
switchport access vlan 22
switchport mode access
duplex auto
spanning-tree portfast
end

Rack1SW2#sh run int e1/0

!
interface Ethernet1/0
switchport access vlan 43
switchport mode access
duplex auto
spanning-tree portfast
end

Rack1SW3#sh run int e0/0

!
interface Ethernet0/0
switchport access vlan 43
switchport mode access
duplex auto
spanning-tree portfast
end

Rack1SW4#sh run int e1/0

!
interface Ethernet1/0
switchport access vlan 146
switchport mode access
duplex auto
spanning-tree portfast
end

So far we did

  • Draw the diagram with the help of Show CDP neighbor command
  • Configured Trunks
  • Created VLANs and assigned ports to the VLans.

Now its time to assign IP address to the Devices and ping Directly connected interfaces to confirm  if our Layer 1 and Layer 2 is UP and Running.

Its really important to have the complete understanding of the network Topology.  INE has many labs on individual technology and all of them are based on this Network Diagram. They Use 6 Routers and 4 Switches.

You will notice that INE is using 155.x.y.z network in their topology.

X represents the RACK Number. In this case it is 1.

Y represents the numbering(Connection) between the devices. For ex: Link connects between R2 and R3 then Y would be 23.

It connection between R1,R4 and R6 then Y=146 etc.

Z represents the Router(Device) Number.

R1–1

R2–2

R3–3

R4–4

R5 — 5

R6 — 6

SW1 – 7

SW2 – 8

SW3 – 9

SW4 — 10

 

Now If you look at the above numbering you will find it very easy understanding the IP address used in the network. If connection between R6 and SW1 then the Ip subnet would be 155.1.67.z ( On R6 z=6 and on SW1 z=7).

So looking at the Logical Topology we need to configure the below IP address on the Devices. All the IP address subnet mask is /24.

On R1

Ethernet0/0—>155.1.146.1/24
Serial1/0—>155.1.0.1/24
Serial1/0.1–>155.1.0.1/24
Serial1/1—>155.1.13.1/24
Loopback0–>150.1.1.1/24

on R2

Ethernet0/0–>192.10.1.2/24
Serial1/0–>155.1.0.2/24
Serial1/0.1–>155.1.0.2/24
Serial1/1–>155.1.23.2/24
Loopback0–>150.1.2.2/24

R3

Ethernet0/0–>155.1.37.3
Serial1/0–>  155.1.0.3
Serial1/0.1–>155.1.0.3
Serial1/2–>  155.1.13.3
Serial1/3–>  155.1.23.3
Loopback0–>  150.1.3.3

R4

Ethernet0/0–>204.12.1.4
Ethernet0/1–>155.1.146.4
Serial1/0–>  155.1.0.4
Serial1/0.1–>155.1.0.4
Serial1/1–>  155.1.45.4
Loopback0–>  150.1.4.4

R5

Ethernet0/0–>155.1.58.5
Ethernet0/1–>155.1.5.5
Serial1/0–>  155.1.0.5
Serial1/1–>  155.1.45.5
Loopback0–>  150.1.5.5

R6
Ethernet0/0.67–>155.1.67.6
Ethernet0/0.146–>155.1.146.6
Serial1/0–>  54.1.1.6
Loopback0–>  150.1.6.6
SW1
Ethernet0/3–>155.1.37.7
Loopback0–>  150.1.7.7
Vlan7–>      155.1.7.7
Vlan67–>     155.1.67.7
Vlan79–>     155.1.79.7

SW2
Interface–>  IP-Address
Ethernet4/0–>155.1.108.8
Loopback0–>  150.1.8.8
Vlan8–>      155.1.8.8
Vlan58–>     155.1.58.8

SW3
Loopback0–>  150.1.9.9
Vlan9–>      155.1.9.9
Vlan79–>     155.1.79.9

SW4
Ethernet3/0–>155.1.108.10
Loopback0–>  150.1.10.10
Vlan10–>     155.1.10.10

Verification :

Rack1SW1#show mac address-table
Mac Address Table
——————————————-

Vlan    Mac Address       Type        Ports
—-    ———–       ——–    —–
58    aabb.cc00.0500    DYNAMIC     Et1/1
58    aabb.cc80.0800    DYNAMIC     Et2/0
146    aabb.cc00.0100    DYNAMIC     Et0/1
146    aabb.cc00.0410    DYNAMIC     Et4/0
146    aabb.cc00.0600    DYNAMIC     Et2/0
5    aabb.cc00.0510    DYNAMIC     Et3/0
8    aabb.cc80.0800    DYNAMIC     Et2/0
9    aabb.cc80.0900    DYNAMIC     Et3/0
10    aabb.cc80.0a00    DYNAMIC     Et4/0
22    aabb.cc00.0200    DYNAMIC     Et2/0
22    aabb.cc00.0c00    DYNAMIC     Et2/0
43    aabb.cc00.0400    DYNAMIC     Et2/0
43    aabb.cc00.0d00    DYNAMIC     Et3/0
67    aabb.cc00.0600    DYNAMIC     Et2/0
79    aabb.cc80.0900    DYNAMIC     Et3/0
Total Mac Addresses for this criterion: 15

 

Rack1SW2#show mac address-table
Mac Address Table
——————————————-

Vlan    Mac Address       Type        Ports
—-    ———–       ——–    —–
22    aabb.cc00.0200    DYNAMIC     Et0/2
22    aabb.cc00.0c00    DYNAMIC     Et0/0
43    aabb.cc00.0400    DYNAMIC     Et1/0
43    aabb.cc00.0d00    DYNAMIC     Et2/0
1    aabb.cc00.0600    DYNAMIC     Et1/2
5    aabb.cc00.0510    DYNAMIC     Et2/0
7    aabb.cc80.0700    DYNAMIC     Et2/0
9    aabb.cc80.0900    DYNAMIC     Et2/0
10    aabb.cc80.0a00    DYNAMIC     Et2/0
58    aabb.cc00.0500    DYNAMIC     Et2/0
67    aabb.cc00.0600    DYNAMIC     Et1/2
67    aabb.cc80.0700    DYNAMIC     Et2/0
79    aabb.cc80.0700    DYNAMIC     Et2/0
79    aabb.cc80.0900    DYNAMIC     Et2/0
146    aabb.cc00.0100    DYNAMIC     Et2/0
146    aabb.cc00.0410    DYNAMIC     Et2/0
146    aabb.cc00.0600    DYNAMIC     Et1/2
Total Mac Addresses for this criterion: 17
Rack1SW2#

 

Rack1SW3#show mac address-table
Mac Address Table
——————————————-

Vlan    Mac Address       Type        Ports
—-    ———–       ——–    —–
5    aabb.cc00.0510    DYNAMIC     Et1/1
43    aabb.cc00.0400    DYNAMIC     Et2/0
43    aabb.cc00.0d00    DYNAMIC     Et0/0
7    aabb.cc80.0700    DYNAMIC     Et2/0
8    aabb.cc80.0800    DYNAMIC     Et2/0
10    aabb.cc80.0a00    DYNAMIC     Et2/0
22    aabb.cc00.0200    DYNAMIC     Et2/0
22    aabb.cc00.0c00    DYNAMIC     Et2/0
58    aabb.cc00.0500    DYNAMIC     Et2/0
58    aabb.cc80.0800    DYNAMIC     Et2/0
67    aabb.cc00.0600    DYNAMIC     Et2/0
67    aabb.cc80.0700    DYNAMIC     Et2/0
79    aabb.cc80.0700    DYNAMIC     Et2/0
146    aabb.cc00.0100    DYNAMIC     Et2/0
146    aabb.cc00.0410    DYNAMIC     Et2/0
146    aabb.cc00.0600    DYNAMIC     Et2/0
Total Mac Addresses for this criterion: 16

Rack1SW4#show mac address-table
Mac Address Table
——————————————-

Vlan    Mac Address       Type        Ports
—-    ———–       ——–    —–
146    aabb.cc00.0100    DYNAMIC     Et2/0
146    aabb.cc00.0410    DYNAMIC     Et1/0
146    aabb.cc00.0600    DYNAMIC     Et2/0
5    aabb.cc00.0510    DYNAMIC     Et2/0
7    aabb.cc80.0700    DYNAMIC     Et2/0
8    aabb.cc80.0800    DYNAMIC     Et2/0
9    aabb.cc80.0900    DYNAMIC     Et2/0
22    aabb.cc00.0200    DYNAMIC     Et2/0
22    aabb.cc00.0c00    DYNAMIC     Et2/0
43    aabb.cc00.0400    DYNAMIC     Et2/0
43    aabb.cc00.0d00    DYNAMIC     Et2/0
58    aabb.cc00.0500    DYNAMIC     Et2/0
58    aabb.cc80.0800    DYNAMIC     Et2/0
67    aabb.cc00.0600    DYNAMIC     Et2/0
67    aabb.cc80.0700    DYNAMIC     Et2/0
79    aabb.cc80.0700    DYNAMIC     Et2/0
79    aabb.cc80.0900    DYNAMIC     Et2/0
Total Mac Addresses for this criterion: 17

Rack1R1#ping 255.255.255.255 repeat 2
Type escape sequence to abort.
Sending 2, 100-byte ICMP Echos to 255.255.255.255, timeout is 2 seconds:

Reply to request 0 from 155.1.146.6, 3 ms
Reply to request 0 from 155.1.0.5, 116 ms
Reply to request 0 from 155.1.13.3, 7 ms
Reply to request 0 from 155.1.146.4, 5 ms
Reply to request 1 from 155.1.146.4, 2 ms
Reply to request 1 from 155.1.0.5, 39 ms
Reply to request 1 from 155.1.13.3, 6 ms
Reply to request 1 from 155.1.146.6, 2 ms

Rack1R2#ping 255.255.255.255 re 2
Type escape sequence to abort.
Sending 2, 100-byte ICMP Echos to 255.255.255.255, timeout is 2 seconds:

Reply to request 0 from 192.10.1.254, 6 ms
Reply to request 0 from 155.1.0.5, 99 ms
Reply to request 0 from 155.1.23.3, 11 ms
Reply to request 1 from 192.10.1.254, 2 ms
Reply to request 1 from 155.1.0.5, 17 ms
Reply to request 1 from 155.1.23.3, 11 ms

Rack1R3#ping 255.255.255.255 re 2
Type escape sequence to abort.
Sending 2, 100-byte ICMP Echos to 255.255.255.255, timeout is 2 seconds:

Reply to request 0 from 155.1.37.7, 1 ms
Reply to request 0 from 155.1.0.5, 40 ms
Reply to request 0 from 155.1.23.2, 6 ms
Reply to request 0 from 155.1.13.1, 6 ms
Reply to request 1 from 155.1.37.7, 1 ms
Reply to request 1 from 155.1.0.5, 57 ms
Reply to request 1 from 155.1.23.2, 17 ms
Reply to request 1 from 155.1.13.1, 16 ms

Rack1R4#
Rack1R4#ping 255.255.255.255 re 2
Type escape sequence to abort.
Sending 2, 100-byte ICMP Echos to 255.255.255.255, timeout is 2 seconds:

Reply to request 0 from 204.12.1.254, 5 ms
Reply to request 0 from 155.1.0.5, 54 ms
Reply to request 0 from 155.1.146.6, 10 ms
Reply to request 0 from 155.1.146.1, 6 ms
Reply to request 0 from 155.1.45.5, 6 ms
Reply to request 1 from 155.1.146.1, 3 ms
Reply to request 1 from 155.1.0.5, 79 ms
Reply to request 1 from 155.1.45.5, 11 ms
Reply to request 1 from 204.12.1.254, 6 ms
Reply to request 1 from 155.1.146.6, 6 ms

Rack1R5#ping 255.255.255.255 re 2
Type escape sequence to abort.
Sending 2, 100-byte ICMP Echos to 255.255.255.255, timeout is 2 seconds:

Reply to request 0 from 155.1.58.8, 4 ms
Reply to request 0 from 155.1.0.1, 191 ms
Reply to request 0 from 155.1.0.4, 85 ms
Reply to request 0 from 155.1.45.4, 8 ms
Reply to request 1 from 155.1.58.8, 1 ms
Reply to request 1 from 155.1.0.1, 215 ms
Reply to request 1 from 155.1.0.4, 126 ms
Reply to request 1 from 155.1.45.4, 6 ms

Rack1R6#ping 255.255.255.255 re 2
Type escape sequence to abort.
Sending 2, 100-byte ICMP Echos to 255.255.255.255, timeout is 2 seconds:

Reply to request 0 from 155.1.67.7, 2 ms
Reply to request 0 from 54.1.2.254, 88 ms
Reply to request 0 from 54.1.1.254, 88 ms
Reply to request 0 from 54.1.3.254, 88 ms
Reply to request 0 from 155.1.146.4, 2 ms
Reply to request 0 from 155.1.146.1, 2 ms
Reply to request 1 from 155.1.67.7, 3 ms
Reply to request 1 from 54.1.2.254, 104 ms
Reply to request 1 from 54.1.1.254, 104 ms
Reply to request 1 from 54.1.3.254, 104 ms
Reply to request 1 from 155.1.146.4, 4 ms
Reply to request 1 from 155.1.146.1, 3 ms
Rack1R6#

Rack1SW1#ping 255.255.255.255 re 2
Type escape sequence to abort.
Sending 2, 100-byte ICMP Echos to 255.255.255.255, timeout is 2 seconds:

Reply to request 0 from 155.1.37.3, 5 ms
Reply to request 0 from 155.1.79.9, 6 ms
Reply to request 0 from 155.1.67.6, 5 ms
Reply to request 1 from 155.1.37.3, 6 ms
Reply to request 1 from 155.1.67.6, 6 ms
Reply to request 1 from 155.1.79.9, 6 ms

Rack1SW2#ping 255.255.255.255 re 2
Type escape sequence to abort.
Sending 2, 100-byte ICMP Echos to 255.255.255.255, timeout is 2 seconds:

Reply to request 0 from 155.1.108.10, 8 ms
Reply to request 0 from 155.1.58.5, 8 ms
Reply to request 1 from 155.1.108.10, 2 ms
Reply to request 1 from 155.1.58.5, 2 ms

Rack1SW3#ping 255.255.255.255 re 2
Type escape sequence to abort.
Sending 2, 100-byte ICMP Echos to 255.255.255.255, timeout is 2 seconds:

Reply to request 0 from 155.1.79.7, 3 ms
Reply to request 1 from 155.1.79.7, 20 ms

Rack1SW4#ping 255.255.255.255 re 2
Type escape sequence to abort.
Sending 2, 100-byte ICMP Echos to 255.255.255.255, timeout is 2 seconds:

Reply to request 0 from 155.1.108.8, 1 ms
Reply to request 1 from 155.1.108.8, 2 ms

Hope this Helps 🙂

 

3 thoughts on “Understanding INE Logical Topology and configuration.

  1. Pingback: Understanding INE Logical Topology and configuration. | maftabmemon

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s