Cisco – How to draw a layer 2 (link layer) network map containing Cisco and *NIX boxes

ciscocisco-catalystmappingnetworkingsolaris

I've been tasked with drawing a layer 2 network map of our very small datacenter network.

There is one 1841 cisco router, two 3560 cisco catalyst switches and 4 solaris sunfire T-1000 boxes.

I have logged in to the cisco boxes and downloaded the running configuration files for all 3. I have also gotten the output of ifconfig -a for the 4 solaris boxes.

my question is: what reading/learning should I do now to put it all together? Any tips?

I was looking at tools such as lanmap2 but that is for linux, not SunOS and I don't know if I could recompile it successfully myself.

I understand intermediate networking, but I'm not a routing guy. I know a VLAN is a way to segregate groups of ports in different switches in their own subnetworks and I hear that a trunk is a connection between two routers that conveys VLAN information but that's the extent of my knowledge on those two topics.

Best Answer

This answer includes a simple LAN diagram that could serve as a template for your network; note that the colors (green / pink / orange) indicate different vlans.

Typically you want to include details like switch / router port numbers, vlan information, IP addressing / netmask, hostnames, and the port name of the interface on the server.

If you don't have a copy of Visio, you can use Inkscape to generate drawings. If you are adventurous, you can even build inkscape-compatible copies of Cisco's networking icons

Related Solutions

Switch – Layer 2 segmentation and network diameter

Distribution layer is layer 3, right? So yes, they are talking about limiting the size of your layer 2 network. Remember that broadcasts get sent to everyone on your layer 2 network, so segmenting it with routers or layer 3 capable switches helps keep things flowing. VLANs are one way to achieve this. Also, STP can cause issues when the layer 2 domain is too big. Just remember that switching is great, but routing is better suited for large networks.

Cisco Route-Map Multiple ACL Match (Logical AND)

Easiest way in my opinion is to setup an access-list with all the matches you need and put that in the route-map.

EDIT

Disclaimer: I'm just guessing here.

You can try this, assuming access-list 100 for sources and access-list 110 for destinations:

Here you revert the logic of the access-lists:

access-list 100 deny ip 10.0.0.0 255.255.255.0 any
access-list 100 permit any

access-list 110 deny ip any 192.168.0.0 255.255.255.0
access-list 110 permit any

and then use deny on your route-map (so if the access-list permits, then the rule fails):

route-map TEST deny 10
   match ip address 100
route-map TEST deny 20
   match ip address 110
route-map TEST permit 30
   set vrf TESTVRF

The logic behind this is:

if source_address is not 10.0.0.0/24 {
    fail
} else {
    if destination_address is not 192.168.0.0/24 {
        fail
    } else {
        set vrf TESTVRF
    }
}

Basically it checks first if source is permitted (via access-list 100), if permitted then it checks if destination is permitted (access-list 101), at last if BOTH are permitted set the vrf.

Then you can easily permit N different source networks in access-list 100 and M different destination networks in access-list 101.

Best Answer

Related Solutions

Switch – Layer 2 segmentation and network diameter

Cisco Route-Map Multiple ACL Match (Logical AND)

Related Topic