- If you need clarification, ask it in the comment box above.
- Better answers use proper spelling and grammar.
- Provide details, support with references or personal experience.
Tell us some more! Your answer needs to include more details to help people.You can't post answers that contain an email address.Please enter a valid email address.The email address entered is already associated to an account.Login to postPlease use English characters only.
Tip: The max point reward for answering a question is 15.
I'm going to assume you can get in the command line interface. Go into the command mode (type "config t" with out the quotes ) then type "ip http server" press enter, type exit to get out of command mode and then "write memory" to save your configuration. Remember, vlan 1 on the switch MUST have a IP address for you to be able to access the web interface.
I have twoWS-C3560V2-48TS-S routers (R1 and R2); R1
has the full BGP table and some local connections to. They are all being
advertise to it's iBGP neighour R2. I can't find a command that I can run on R2
that will show the number of prefixes learnt from R1 that are internal to the
local AS only. It just says 425~k which is all the Internet routes and the
What command can I use for
the local AS originated networks has
AS path attribute empty.
So you could define an ip as-path
acl matching an empty string
ip as-path access-list 1 permit ^$
then you can invoke the as-path
access-list as a filter action on show ip bgp on R2
show ip bgp filter-list 1
BGP command reference http://www.cisco.com/en/US/docs/ios-xml/ios/iproute_bgp/command/bgp-s1.html#GUID-2618748E-42ED-495A-875C-D398A02D79F9
At this point it is enough to count
the lines in show ip bgp filter-list 1 output to count the routes that are originated
in the local AS at R1 WS-C3560X-24P-L Price and received on R2 and installed on R2.
Did you use the command: ip http server ? See page 501 in the manual.
I would not recommend setting up a network switch with password-free access to the internet. You should at the very least limit access to a small subset of IP addresses (e.g. your network group's machines). The best practice is to use ssh communications or https with the web browser, otherwise anyone with a well-placed sniffer can read your clear-text traffic.
First, be sure to assign an ip address(in the proper subnet) to each VLAN.
Second, use the ip helper-address command in the context of each VLAN, the address used should be the address of the DHCP server
Third, Add a scope for each additional VLAN on the DHCP server.
The switch will route the DHCP request to the proper server based on the ip helper-address command parameter and based on the ip address of the VLAN that is passed tot he server, a DHCP address in the proper subnet is automatically configured.