Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
- Cisco Community
- :
- About Mark Mattix
03-26-2019
Mark Mattix
Explorer
CCNA
CCNA: Wireless
CCNA: Security
CompTIA A+, Network+ and Security+
Recent Badges
Stats
Member since
02-22-2012
256
Posts
30
Helpful
1
Solution
Created by
Mark Mattix
in Other Data Center Subjects
in Other Data Center Subjects
03-12-2018
09:12 AM
03-12-2018
09:12 AM
Hello, Could someone help me determine if OTV is supported on the Nexus 3K line of switches, specifically the 31108TC-V? I do not see the 3K line in the Cisco featureset navigator. Thanks a lot for your help!
*Update* Heard back from my Cisco rep OTV is not supported on the 3K line. Can anyone recommend a type of DCI technology that's supported on the 3K line?
... View more
Labels:
08-09-2017
06:20 AM
Thanks again for your help Jon. I finally understand what I was doing wrong. Luckily my understanding of ACLs and direction was correct but the flow of traffic on SVIs is where I was having a problem... I appreciate your help!
... View more
08-02-2017
02:34 PM
That does help, I need some time to reflect on this... lol Thank you!
... View more
08-02-2017
01:48 PM
The client traffic from 192.168.1.0 would physically come in to the device via it's corresponding interface but isn't that traffic also going into the virtual SVI?
... View more
08-02-2017
01:39 PM
Sorry to keep bothering you about this but I thought I understood how this worked. Client traffic from 192.168.1.0 would be the source and it would come IN to the management SVI, right? Once it's in I allowed it to go to any ip with the port of 443.
... View more
08-02-2017
01:17 PM
So you think this should be applied to the SVI but outbound? I thought outbound meant traffic leaving the SVI?
ip access-list extended Management-IN permit tcp 192.168.1.0 0.0.255.255 any eq 443 deny ip any any log
... View more
08-02-2017
12:43 PM
Sorry I edited my prior comment, my client device is on 192.168.1.0 and the server is on 10.10.1.0. These ACLs are being applied to the Server 10.10.1.0 SVI.
According to this:
ip access-list extended Management-IN permit tcp 192.168.1.0 0.0.255.255 any eq 443 deny ip any any log
Doesn't this mean my client from 192.168.1.0 sourcing from any port going to my server on 10.10.1.0 listening on 443 should be allowed? Do you think I would need the reverse statement as well to allow the server to come into the SVI and back out to the client? Thank you!
... View more
08-02-2017
11:39 AM
I guess I should also state that this device is actually a Brocade L3 switch, I'm assuming they work the same though...
... View more
08-02-2017
11:39 AM
The server I'm trying to control access to is directly on the 10.10.1.0 network. I'm applying my ACL in and out on the 10.10.1.0 SVI.
... View more
08-02-2017
10:15 AM
Mark, can you notice anything I might be doing wrong with this ACL?
interface ve 1 ip access-group Management-IN in ip access-group Management-OUT out
ip access-list extended Management-IN permit tcp 192.168.1.0 0.0.255.255 any eq 443 deny ip any any log ip access-list extended Management-OUT permit tcp any eq 443 192.168.1.0 0.0.255.255 deny ip any any
I can connect to my server with https when the acl is not applied but lose connection when I apply it. I have additional statements that are similar but for port 80 as well. Thanks
... View more
07-31-2017
11:41 AM
Thanks a lot for that information Mark. When you state a source for SSH does this mean management traffic will only be allowed out that interface, like Gi0? Or does this mean if I attempted to run an SSH session on the device it would source that session from what I specified?
Would you be able to post an example of the ACL's you used for traffic going in and out? I appreciate it!
... View more
07-31-2017
09:18 AM
Hello, I'm looking for recommendations for the best way to design a management network for one of my locations. Some devices have built in management interfaces like my 2960s and other devices like my 3925E do not have specific interfaces so I planned to use gi0/3 as a management port.
My plan is to create a management vlan on my L3 core switch and then connect all of the other components to this management vlan and only allow SSH into the vlan.
What methods can I use to insure data traffic doesn't attempt to use the management port on a device like the 3925E which will have a another interface for data traffic? Should I be doing this a different way? Thanks for the advice!
... View more
Labels:
03-12-2018
Hello, Could someone help me determine if OTV is supported on the Nexus
3K line of switches, specifi...
08-09-2017
Thanks again for your help Jon. I finally understand what I was doing
wrong. Luckily my understandin...
08-02-2017
The client traffic from 192.168.1.0 would physically come in to the
device via it's corresponding in...
08-02-2017
Sorry to keep bothering you about this but I thought I understood how
this worked. Client traffic fr...
08-02-2017
So you think this should be applied to the SVI but outbound? I thought
outbound meant traffic leavin...
08-02-2017
Sorry I edited my prior comment, my client device is on 192.168.1.0 and
the server is on 10.10.1.0. ...
08-02-2017
I guess I should also state that this device is actually a Brocade L3
switch, I'm assuming they work...
08-02-2017
The server I'm trying to control access to is directly on the 10.10.1.0
network. I'm applying my ACL...
08-02-2017
Mark, can you notice anything I might be doing wrong with this ACL?
interface ve 1ip access-group Ma...
07-31-2017
Thanks a lot for that information Mark. When you state a source for SSH
does this mean management tr...
Public Statistics
| Date Registered | 02-22-2012 08:07 AM |
| Date Last Visited | 03-26-2019 05:01 PM |
| Total Messages Posted | 256 |
| Total Helpful Votes Received | 30 |
Helpful Votes Given To
| User | Helpful Count |
|---|---|
| 25 | |
| 10 | |
| 5 | |
| 5 | |
| 5 |
.jpg "Hall of Fame Guru"){kind=icon}
.jpg "VIP Mentor"){kind=icon}
Helpful Votes From
